-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
proposal: cmd/go: add work
package pattern matching all packages in work modules
#71294
Labels
Milestone
Comments
Related Issues (Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
Change https://go.dev/cl/643235 mentions this issue: |
slsyy
added a commit
to slsyy/testfixtures
that referenced
this issue
Feb 2, 2025
some shenaningas were introduced to run tests&lint over all modules Probably it won't be necessary, when golang/go#71294 is resolved
slsyy
added a commit
to slsyy/testfixtures
that referenced
this issue
Feb 2, 2025
some shenaningas were introduced to run tests&lint over all modules Probably it won't be necessary, when golang/go#71294 is resolved
slsyy
added a commit
to slsyy/testfixtures
that referenced
this issue
Feb 2, 2025
some shenaningas were introduced to run tests&lint over all modules Probably it won't be necessary, when golang/go#71294 is resolved
slsyy
added a commit
to slsyy/testfixtures
that referenced
this issue
Feb 2, 2025
some shenaningas were introduced to run tests&lint over all modules Probably it won't be necessary, when golang/go#71294 is resolved
This proposal has been added to the active column of the proposals project |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Proposal Details
I'm making this proposal to resolve #50745
This proposal is to add a new package meta-pattern to join the already existing
all
,std
,cmd
, andtool
patterns. The work pattern would match all packages in the work (formerly called main) modules: either the single work module in module mode or the set of workspace modules in workspace mode.This would allow for a single pattern to build or test all of those packages, similar to using
./...
at the root of a module to test a single module's packages.cc @hyangah @rsc @samthanawalla
The text was updated successfully, but these errors were encountered: