> Start working on a new change based on the <main> branch -- jj co main
Did you consider the recent git nomenclature change to use "switch" for branch operations, and "co" for file operations? I actually can't tell from so deep in my "git Stockholm syndrome" whether that distinction is really hard on new users or not, but the fact that git expended the energy meant they thought it was meaningful
And, do you have plans on supporting signed commits, either via gpg or the newfound SSH key signing?
I'm super excited to try out the conflict resolution mechanism, because that's a major painpoint for my long-lived PR branches
The git comparison docs have:
> Start working on a new change based on the <main> branch -- jj co main
Did you consider the recent git nomenclature change to use "switch" for branch operations, and "co" for file operations? I actually can't tell from so deep in my "git Stockholm syndrome" whether that distinction is really hard on new users or not, but the fact that git expended the energy meant they thought it was meaningful
And, do you have plans on supporting signed commits, either via gpg or the newfound SSH key signing?
I'm super excited to try out the conflict resolution mechanism, because that's a major painpoint for my long-lived PR branches