"If you commit on this branch, GitButler will throw it away." But does it have to?

[seanf]

Would it be possible for GitButler to take any extra commits found in gitbutler/workspace after "Back to workspace" and preserve these commits in a new (applied) branch?

A lot of my normal git workflow involves JetBrains tools, sometimes hunk-by-hunk commits (JetBrains has nice UI for this), and Copilot-generated commit messages, and it's a shame to have to give them up to use GitButler.

I can use git switch before committing, but it's more friction, plus it takes away the other applied branches in GitButler's workspace.

[Byron]

Thanks a lot for bringing this up.
It's absolutely true that the current behaviour isn't very desirable, as it will effectively suggest to re-integrate the changes again, collapsing and ignoring the commits that contain them. This is the code responsible for it, and it's nothing but a crutch.

It is definitely planned to make this smooth, but it needs UI support and there is still more fundamental things that need attention. However, when this is tackled I could imagine that there is a 'mode' that allows to quickly drag&drop commits to any location in the workspace.

[seanf]

Incidentally, I think #11866 will help (at least when I don't need to apply multiple branches).