-
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
cmd/go: add work
package pattern matching all packages in work modules
#71294
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: |
some shenaningas were introduced to run tests&lint over all modules Probably it won't be necessary, when golang/go#71294 is resolved
some shenaningas were introduced to run tests&lint over all modules Probably it won't be necessary, when golang/go#71294 is resolved
some shenaningas were introduced to run tests&lint over all modules Probably it won't be necessary, when golang/go#71294 is resolved
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 |
Have all remaining concerns about this proposal been addressed? The propsal is to add a new metapackage 'work' (others include 'std', 'cmd', 'all') that will expand to all packages in the current workspace, or the current module when there is no go.work (a "single-module workspace"). |
Based on the discussion above, this proposal seems like a likely accept. The propsal is to add a new metapackage 'work' (others include 'std', 'cmd', 'all') that will expand to all packages in the current workspace, or the current module when there is no go.work (a "single-module workspace"). |
No change in consensus, so accepted. 🎉 The propsal is to add a new metapackage 'work' (others include 'std', 'cmd', 'all') that will expand to all packages in the current workspace, or the current module when there is no go.work (a "single-module workspace"). |
work
package pattern matching all packages in work moduleswork
package pattern matching all packages in work modules
Change https://go.dev/cl/658495 mentions this issue: |
For #71294 Fixes #50745 Change-Id: Iff05e98ac860a1764d4c59572f9abc3ae8d9c5fb Reviewed-on: https://go-review.googlesource.com/c/go/+/658495 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Alan Donovan <adonovan@google.com>
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: