Comment on Highlights from Git 2.23parentComments−wodenokoto7yBut I want to switch to my new branch. One of these commands will have to do double duty.Either switch/checkout will create or branch will switch.I don’t see why choosing one for double duty is inherently worse than the other.But I do consider your proposal of `git branch —create` as a poor command for create and switch branch.−masklinn7yFWIW in their proposal `git branch -c` would be `git branch --checkout` not `git branch --create`, which is what `git branch <name>` does.The `git checkout -b` and `git switch -c` docs specifically note that they're shortcuts for going a git branch then a git checkout/switch.
Comments
But I want to switch to my new branch. One of these commands will have to do double duty.
Either switch/checkout will create or branch will switch.
I don’t see why choosing one for double duty is inherently worse than the other.
But I do consider your proposal of `git branch —create` as a poor command for create and switch branch.
FWIW in their proposal `git branch -c` would be `git branch --checkout` not `git branch --create`, which is what `git branch <name>` does.
The `git checkout -b` and `git switch -c` docs specifically note that they're shortcuts for going a git branch then a git checkout/switch.