I seem to have found my footing with #Jujutsu, a new frontend for #Git.
The most important change is that my working copy is committed in the current change as soon as I run any Jujutsu command.
This means I can't have a file that's lying around while I move commit to commit. I have to split that file into its own commit, and make that commit an ancestor to any place that needs the file. It's an adjustment, sure.
I am also a user of #Sapling. I enjoy Sapling direct GitHub integration.
=> More informations about this toot | More toots from francois@ruby.social
[#]Sapling's GitHub integration is really nice, because I can edit the commit description and sl push
and the PR description is updated to match the commit description. That's something I really, really like.
The jury's still out on whether I'm staying on Jujutsu or switching back to Sapling. I am giving Jujutsu another week or two of daily driver before making a final decision.
=> More informations about this toot | More toots from francois@ruby.social
text/gemini
This content has been proxied by September (ba2dc).