Well, jj is actually very nice in this regard, because:
1. it works on top of git — you keep using all the same infrastructure (GitHub, etc.)
2. in your local repositories you still have access to git-tools, as jj maintains git and its own states in sync.
After all of these months with jj I still find myself using GitUp when I need to review a long chain of commits or do some quick repo-archeology.
And, from time to time, I even use Idea's merge tools because their "magic wand" saves a lot of time.
1. it works on top of git — you keep using all the same infrastructure (GitHub, etc.) 2. in your local repositories you still have access to git-tools, as jj maintains git and its own states in sync.
After all of these months with jj I still find myself using GitUp when I need to review a long chain of commits or do some quick repo-archeology. And, from time to time, I even use Idea's merge tools because their "magic wand" saves a lot of time.
I mentioned this in the first part of series