I find it incredibly useful as an individual contributor opening many PRs on a single upstream project. I can rebase all my PRs onto new upstream changes in one go, I can easily keep the commit graph neat, I can easily squash changes down into specific PRs while keeping my working tree positioned after they all merge together. Really speeds up my workflow, it's awesome. And it's really cool that merge conflicts don't block operations. It's really limiting that git has only one active branch at a time.
> I probably subconsciously steer away from due to the awkwardness.
I think if I need to rebase a PR enough while waiting for merge that it's a coordination issue and maybe too much churn in the codebase. There shouldn't be a need to do so. Not sure I'd blame git for that.
(Do let me know if this has changed, but I've seen any other kind of merge result in the yellow "Unverified" status on GitHub, as I have the thing turned on that requires all commits from me to be signed with my own key.)
- e.g. tracks everything by default; this is an advantage compared to "oops I forgot to check it in".
- e.g. reworking feature branches is more natural in jj compared to rebasing in git.
Clearly other people are delighted with jj though.
Perhaps the value becomes clear on larger teams, big monorepos?