Merged
Conversation
andrewnester
approved these changes
Feb 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Adding
go.workfiles to the.gitignore, as we don't use monorepos and don't need it in to be tracked.See example in .gitignore template collection: https://github.com/github/gitignore/blob/main/Go.gitignore#L23
Why
It is convenient when you need to run
go runfrom any directory, e.g. if I have my bundle collection I can doWithout
go.workI need to either build the CLI, or configure launch targets in IDE, or put a bundle inside the CLI repo. Usinggo runis slightly more convenient, especially when using with agentsTests