RFC: branch move
: document that we don't want to support -f
for --from
#4655
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.
Reasoning TLDR: we don't want it confused with --force. This follows up on #4612, which did add these shortcuts for
jj move
.I was initially going to add them, but people imagining
jj branch move --force
(as people were worried in #4612) is a real possibility, sincejj branch move --allow-backwards
is a thing.The reason I would like us to think about this is that I was looking at adding some shorthands like
jj b m
to git-comparison.md (just a few, where thejj
version looks especially long), and I'm not sure whether to use-t
or--to
there.