Remove the short option -o for --overwrite #1483
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Remove the short option -o for --overwrite.
Why
The --overwrite option is destructive and users can lose files and hard work by using it. We should make it very explicit and obvious when users are doing things that could cause them to lose work.
A second reason is that we should reserve short options for the most common workflows, and the workflows where someone can look at the short command in context and almost be able to guess as to what that short option means or at least the cognitive load of remembering what it means should be matched with the value the user gets out of having to remember. The overwrite workflow is unlikely to be used by many people, and on something like a init command the -o option is pretty ambiguous.