I See a Future in Jj

Re:I See a Future in Jj by constantius on Wednesday October 22, 2025 @04:41PM (#45674881)

I have a question and you might have an idea about this:

I have a workflow where I have my main and a bunch of branches that are children of other branches. So: main, branch_a, branch_a_1, branch_a_2, branch_a_1_x, etc. Probably not a good workflow, but that's what I do.

I keep editing old commits in my branches to have clean, atomic commits, which fucks up my branch structure and I need to cascade-rebase everything manually.

Do I understand correctly that jj does it automatically?

[ Parent | on HN ]

Re:I See a Future in Jj by steveklabnik on Wednesday October 22, 2025 @04:50PM (#45674973)

That's correct, it will do the cascade rebase of everything automatically.

[ Parent | on HN ]

Re:I See a Future in Jj by constantius on Friday October 24, 2025 @12:41PM (#45696367)

Thanks Steve, and for the tutorial too!

[ Parent | on HN ]

Re:I See a Future in Jj by 1718627440 on Thursday October 23, 2025 @04:18AM (#45679472)

git rebase --update-refs

[ Parent | on HN ]

Re:I See a Future in Jj by martinvonz on Thursday October 23, 2025 @09:50AM (#45681810)

That won't update sibling branches

[ Parent | on HN ]

Re:I See a Future in Jj by 1718627440 on Monday November 03, 2025 @02:38PM (#45803437)

It won't update (sibling) branches, that are checked out.

      --update-refs, --no-update-refs
           Automatically force-update any branches that point to commits that
           are being rebased. Any branches that are checked out in a worktree
           are not updated in this way.

           If the configuration variable rebase.updateRefs is set, then this
           option can be used to override and disable this setting.

[ Parent | on HN ]

Re:I See a Future in Jj by Iwan-Zotow on Thursday October 23, 2025 @11:32PM (#45690469)

Won't work, only tree

[ Parent | on HN ]