Create branch at bottom of stack (opposite of "create dependent branch")

[jeyj0]

While working on a larger feature, I often realize I want to merge part of my changes before merging the whole thing. Especially if the overall feature is still work-in-progress.

To correctly model this in GitButler, what I need to do is create a branch at the bottom of the stack.

I've done this a few times already with a workaround, but would love to have a dedicated feature that automates the steps that I currently do to achieve it.

Workaround flow (assuming a stack with a single branch; can easily be extended to an arbitrary number though):

1. create dependent branch at top, with a temporary name
2. drag-and-drop all commits from original (bottom) branch into new branch at top
3. rename bottom (original, now empty) branch to intended new branch name
4. rename top (dependent, containing all commits) branch to original branch name

This way, I end up with a new, empty branch at the bottom of the stack. I can now use various gitbutler features to move changes into this branch and create a PR for them.

To visualize the intended feature, I what I'd like to have is an option like "Create dependent branch", maybe called "Create base branch" (naming could certainly be improved), that would take the state from the first image and result in the state of the second image:

[Byron]

Thanks so much for sharing this idea, it's much appreciated!

I think it's fair to say that I heard of features like "Add dependent branch below" and moving entire stack segments (i.e. branches) around. With the latter feature it would be possible to create a new branch on top, and then move it into position where needed.
There is no technical reason these features couldn't exist or would be hard to implement.

[jeyj0]

While showing gitbutler to a colleague, we were actually both surprised moving entire stack segments didn't already work.

And that would also satisfy this idea very well!

[Byron]

That's great to hear! I am thinking that this will be implemented even without an explicit issue, but hope you will feel free to create one: Moving branches into place would be a GitButler way of doing things, but offering to create new dependent branches 'below' and 'above' would certainly be intuitive for some workflows as well, and might be far easier to implement.