Add support for splitting an existing commit

239 votes

This is one of the few missing features that force me to launch a competing git GUI tool.

The use case is that I or someone on my team have accidentally committed multiple unrelated files as a single commit, and upon review wish to clean up the branch history before merging by splitting the single commit into two separate commits.

Under consideration Suggested by: Mark Hastings (16 Jun, '21) • Upvoted: 18 Apr • Comments: 11

Comments: 11

19 Jul, '21
Adam Gregory
This is a very important feature for me. I often re-organise commits on feature branches for large features. It's easy to do with TortoiseGit, and I really miss the feature in GitKraken.
08 Dec, '21
braykov
This is an important part of interactive rebase
1
16 Dec, '21
Johannes
As a new pro user i did not even consider this was not implemented :(
1
07 Jan, '22
Karsten
I think the interactive rebase is among the best features of GitKraken, allowing to split files at a commit makes tons of sense. At the very least, marking a commit for editing (so that you can unstage some files, commit, stage some remaining files, commit etc.) during interactive rebase would be okay for me.
25 Feb, '22
Esteban Martinena Guerrero
Absolutely needed when working on teams. Some free and open-source Git GUI applications already have this, and I see myself switching to it to make these changes every week.
16 Jul, '22
Josh
+1 when maintaining a very large open source project I must often fixup and split commits for new contributors
18 Apr, '23
Rineez Ahmed
This is very useful feature. Smart Git has it.
02 Jan, '24
Vlad
oh no, this feature is also missing (among with "reset file to state in commit")
I seriously start planning to switch to a different git client.
08 Mar, '24
Luke
80% of my needs of a git client would be streamlined if this were implemented—this is a strong reason for considering an alternative tool, as others have suggested.
28 Mar, '24
Dan Vicarel
I don't have experience with the alternative clients mentioned here, but how would this feature even work? How many commits would be generated? Which files would go in which commit? GitKraken already has an Interactive Rebase window. Seems to me they just need to add an "Edit" option to the dropdowns in that window to represent the "edit" command from the command line, as described in the git docs (https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History). In fact, there's another ticket already tracking that: https://feedback.gitkraken.com/suggestions/203766/support-more-interactive-rebase-commands-and-external-rebase-states.
1
06 Sep, '24
Gabriel
This would be amazing to see.