Add support for splitting an existing commit

Comments: 13

Oldest • Newest • Most likes • Fewest likes

• Add a comment
• 07 Jan, '22
  Karsten

  Highlighted comment
  
  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.

  1 Copy link to this comment
• 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.

  2 Copy link to this comment
• 08 Dec, '21
  braykov

  This is an important part of interactive rebase

  2 Copy link to this comment
• 16 Dec, '21
  Johannes

  As a new pro user i did not even consider this was not implemented :(

  2 Copy link to this comment
• 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.

  1 Copy link to this comment
• 16 Jul, '22
  Josh

  +1 when maintaining a very large open source project I must often fixup and split commits for new contributors

  1 Copy link to this comment
• 18 Apr, '23
  Rineez Ahmed

  This is very useful feature. Smart Git has it.

  1 Copy link to this comment
• 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.

  1 Copy link to this comment
• 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.

  1 Copy link to this comment
• 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.

  3 Copy link to this comment
• 06 Sep, '24
  Gabriel

  This would be amazing to see.

  1 Copy link to this comment
• 04 Sep, '25
  Andre Greeff

  I agree with Dan Vicarel on this point, "splitting a commit" (and many more scenarios) would be covered by the suggested found at https://feedback.gitkraken.com/suggestions/203766/support-more-interactive-rebase-commands-and-external-rebase-states.
  
  Lately I've been using GitKraken for _most_ things Git, but the limited interactive rebase functionality means I constantly have to bounce between GitKraken and Fork... Would be really nice to stick to one app.

  1 Copy link to this comment
• 22 Dec, '25
  mephi42

  I make Linux kernel / GCC / QEMU contributions every now and then, and the maintainers on the mailing lists are extremely picky when it comes to deciding what should go into which commit, so I end up reshuffling hunks with interactive rebase quite often. Needless to say, this is annoying and time-consuming. GitKraken already has interactive staging, and plugging it into the "edit" phase of interactive rebase should cover this use case flawlessly.
  
  Today https://github.com/mystor/git-revise makes things a bit better, but `git add -p` UX is still very painful.

  1 Copy link to this comment