-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support workspaces for go #864
Conversation
sergiusens
commented
Oct 3, 2024
- Have you signed the CLA?
63e39ed
to
14b7ed0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks very much Sergio! This is just as we discussed and looks great to me with my limited knowledge on craft plugins. I raised a minor point about not supporting existing go.work files inline.
34eff9b
to
7b221ba
Compare
Signed-off-by: Sergio Schvezov <[email protected]>
We cannot guarantee consistent results, the build should fail at this point until we have a mechanism to validate steps. Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
7b221ba
to
6ec4aa8
Compare
Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
6ec4aa8
to
08cb733
Compare
There is a how do we clean item to deal with, but might need to come later |
Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
@tigarmo sorry about that, there is nothing really left from the original implementation |
Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sergiusens can you talk about the motivation for moving on from the previous implementation to this one?
Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
d709994
to
28f5cc0
Compare
Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to do what was discussed. Ordinarily I would call this an experimental plugin but in the use context it would be rather inconvenient to have to plaster --use-experimental-plugins
everywhere. It should be fine if we properly address global state handling early next cycle.
Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
Co-authored-by: Tiago Nobrega <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>