Introduce auto_confirmed option for 'maintenance uninstall' task #165
Conversation
This file contains hidden or 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
doawoo
reviewed
Jan 11, 2025
src/maintenance.zig
Outdated
Comment on lines
15
to
16
| const confirmed = args.len >= 2 and std.mem.eql(u8, args[1], "confirmed"); | ||
| try do_uninstall(install_dir, confirmed); |
Contributor
There was a problem hiding this comment.
Just a nitpick, but I would prefer this be called the inverse: -no-confirm or something like that.
Author
There was a problem hiding this comment.
i changed the option to --no-confirm :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Usecase:
In some scenario, there is a need to override the cached build with a new build of the same version, without user having to type
ywhen prompted. For example, re-deploy a build in a local test/prod env. This makes scripting easy.