-
Notifications
You must be signed in to change notification settings - Fork 290
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
deploy: Add --no-merge #2081
deploy: Add --no-merge #2081
Conversation
Argh, state shared across the admin base test into uboot. Let's just make it a separate test. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/test sanity |
All of the underlying libostree APIs have supported passing `NULL` for a merge deployment for...a long time. But we never plumbed it up into the CLI. Add a `--no-merge` option to aid people who want to do a "factory reset": ostreedev#1793
OK I just squashed in the same fix as coreos/rpm-ostree#2067 here. |
Nice! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, d4s, jlebon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
All of the underlying libostree APIs have supported passing
NULL
for a merge deployment for...a long time. But we never plumbed
it up into the CLI.
Add a
--no-merge
option to aid people who want to do a "factory reset":#1793