feat(release): allow projects shorthand for single release group #20560
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit c600571. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
JamesHenry
force-pushed
the
release-projects-shorthand
branch
from
ed5d788
to
e452c71
Compare
JamesHenry
force-pushed
the
release-projects-shorthand
branch
from
e452c71
to
b7afb94
Compare
fahslaj
approved these changes
Dec 4, 2023
FrozenPandaz
approved these changes
Dec 4, 2023
ndcunningham
approved these changes
Dec 4, 2023
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Current Behavior
If the user wants to exclude one or more projects from the default behaviour of all library projects, they are forced to define and name a release group to achieve this
Expected Behavior
If the user wants to exclude one or more projects from the default behaviour of all library projects, they can simply specify one or more project matchers at the top level of their release config
Related Issue(s)
Fixes #