Getting started with jj

Over the past few weeks, I have been using jj! This is not the first time I have tried it, but it is the first time it has stuck. For years, my git workflow has used "make a change, then git commit --amend --no-edit && git push --force-with-lease", while on a branch. This meant that my changes would be up to date on the remote with very little latency. PRs would rarely be more than a small number of commits, usually 1, and I would try to keep them as small as possible. Since working with agents, I have found myself switching branch much more frequently. Because of this, I either have to git stash, or make some silly little wip commit to stop my changes from stepping on each other. Enter our new hero, jj! The model here is a bit different. I will not write a huge manual because there are plenty of those, and they are better than anything I would whack into my notes with little thought. Suffice to say, the main thing that appeals to me is that my changes are always committed. Every edit…