Re:The missing introduction to Jujutsu version control
by J_tt on Sunday December 22, 2024 @04:33PM
(#42489317)
Adding onto this, there’s also an experimental feature to move a bookmark as you create new revisions (similar to how a git branch behaves)
Re:The missing introduction to Jujutsu version control
by pkulak on Monday December 23, 2024 @03:05AM
(#42492704)
Oh, that would be nice. I get the reasoning not to, but it would be nice to have the option.
Re:The missing introduction to Jujutsu version control
by stavros on Sunday December 22, 2024 @08:50PM
(#42490994)
What changes the change ID? What constitutes a change? Is a change made up of many commits, or the other way around?
Re:The missing introduction to Jujutsu version control
by Superfud on Monday December 23, 2024 @01:12AM
(#42492226)
A change ID is stable over time as you tweak the message of the change or the files edited by the change. Each of these changes become a new immutable git commit under the hood.
The fact that change ID is stable is very convenient for humans - means you have something explicit to hold on to as everything else may change over time.
This lets you work on things without having to worry about giving it a name. This turns out to be pretty helpful when you're experimenting — just "jj new <revision>" and start editing. If it turns out to be something you want to share, "jj bookmark create <name>" and then you can push it. (You can also push without giving it a name, in which case you'll get a git branch with a name based off of the change id.)
Change IDs stay constant with each change, so you use those as a type of branch name when switching between the features you're working on.