> My team is totally PR based though so if/when doing (Git compatible) feature branches lands in JJ I'm excited to switch.
I'm trying to find the part of the docs that refers to this functionality as missing but I can't -- does jj not have the ability to create, update, pull from, merge branches, etc?
1. Create a fork via GitHub's web UI
2. Clone using the SSH protocol (`jj git clone git@github.com:...`)
3. Make your changes and "commit" (`jj close/commit`)
4. Create a branch pointing to the commit you just created (`jj branch my-feature -r @-`)
5. Push it to your fork (`jj git push`)
So that doesn't seem too onerous, I guess? Maybe the "too many manual steps" are to clean up afterwards. I just tried it in a test repo and deleting the branch from the fork and then `jj git fetch` from there does delete the local branch, but it doesn't abandon the commits, so you need to run `jj abandon` on them if you don't want them anymore.
I'm trying to find the part of the docs that refers to this functionality as missing but I can't -- does jj not have the ability to create, update, pull from, merge branches, etc?