-
Notifications
You must be signed in to change notification settings - Fork 223
Make --no-release exclusive from new --allow flags on app deploy #6783
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
base: main
Are you sure you want to change the base?
Conversation
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success3670 tests passing in 1430 suites. Report generated by 🧪jest coverage report action from b105cfd |
|
We detected some changes at Caution DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release. |

WHY are these changes introduced?
To prevent conflicting/confusing flag combinations from being used together in the
app deploycommand.WHAT is this pull request doing?
Adding an
exclusiveproperty to theno-releaseflag in the deploy command to ensure it cannot be used together with theallow-updatesorallow-deletesflags. This prevents users from specifying contradictory options when deploying an app.How to test your changes?
--no-releaseand--allow-updatesflags--no-releaseand--allow-deletesflagsMeasuring impact
How do we know this change was effective? Please choose one:
Checklist