Support more interactive rebase commands and external rebase states

Comments: 30

Oldest • Newest • Most likes • Fewest likes

• Add a comment
• 06 Oct, '22
  Emil Schoenawa

  Highlighted comment
  
  I for one would also love the availability of the 'edit' command. Being able to attribute changes to commits earlier than the last one is quite crucial in correctly structuring PRs.
  
  I'm running into this need more and more, and the command line for that interactive rebase takes quite a lot of time.

  1 Copy link to this comment
• 25 Aug, '21
  Tom Piddock

  I would also like to highlight that I would happily accept these changes or additions incrementally, being supported one by one in order to preserve as much stability as possible through GitKraken when Interactive Rebasing.
  GitKraken already helps substantially with my day-to-day work in repositories, so this would be that extra layer of polish that would level up the functionality significantly and make my daily workflow so much nicer.

  3 Copy link to this comment
• 11 Jan, '22
  Max Bruckner

  The two things that would help my workflow significantly are:
  * edit
  * fixup
  
  You can currently emulate fixup with squash, but it's quite annoying because you need to delete the text of the squashed commit from the commit message

  12 Copy link to this comment
• 23 Mar, '22
  Dustin

  Totally agree, edit is needed the most from our end :)

  6 Copy link to this comment
• 23 May, '22
  Zoe

  I would love to see "fixup" implemented!

  1 Copy link to this comment
• 22 Jun, '22
  Roman

  Agreed. I'd love to see at least edit and fixup added.

  1 Copy link to this comment
• 30 Jun, '22
  Michał

  Please add edit and fixup (in my case - I always need to remove squashed commit message from description for now). But `edit` is probably the most expected option

  1 Copy link to this comment
• 05 Jul, '22
  Stephen

  I'd also love fixup to be added (all of them really, but fixup is the one I miss the most).

  1 Copy link to this comment
• 08 Aug, '22
  Adam Halesworth

  I would love to have 'edit' available as an interactive rebase command. I prefer to fix/improve things at the point they are introduced into the branch, and this would remove the need to move the commit around to perform an amend. 🙌

  2 Copy link to this comment
• 22 Nov, '22
  Jim Merged

  It would be awesome to be able to do an interactive rebase in Gitkraken, allowing me to EDIT specific commits as well, and not just pick or reword them as is currently supported

  1 Copy link to this comment
• 23 Nov, '22
  Chris Bowie System

  "Interactive rebase with edit mode" (suggested by Jim on 2022-11-22), including upvotes (1) and comments (0), was merged into this suggestion.

  1 Copy link to this comment
• 29 Nov, '22
  Jason M. Gates

  As you're prioritizing the list of interactive rebase options, I'd tackle fixup first. Using squash and editing the commit message only takes an extra second or two, but integrate that over the number of times I fixup, and it at least adds up to an extra coffee break per week :)

  1 Copy link to this comment
• 10 Jan, '23
  Alain D.

  I just migrated from windows / git fork to linux / gitkraken, and I miss the edit option a lot! It’s very useful to split commits before rearranging the history.
  And since git kraken refuses to do anything while an external rebase is in progress, I have to go full CLI for this operation, which is very annoying.

  1 Copy link to this comment
• 09 Feb, '23
  Michał

  It's super sad that I have to use external tool like Fork to interactive reabase with edit option, this one is the most common one!

  1 Copy link to this comment
• 25 May, '23
  Johnny

  Edit and Fixup would be really great; it annoys me I have to switch to my terminal to perform those - everything else in Gitkraken works an absolute treat

  2 Copy link to this comment
• 31 Aug, '23
  Joey Kelroy Admin

  "Please support interactive rebase commands external rebase states - edit" (suggested by bqliang on 2023-08-30), including upvotes (1) and comments (0), was merged into this suggestion.

  3 Copy link to this comment
• 08 Oct, '23
  John Knottenbelt

  +1 on Edit and Fixup.

  2 Copy link to this comment
• 14 Dec, '23
  Jacob Jidell

  +1 on Edit and Fixup as well

  2 Copy link to this comment
• 14 Dec, '23
  Themis

  +1 on Edit. Please :D

  2 Copy link to this comment
• 15 Dec, '23
  Jack Merged

  Definitely agree with this, I frequently spike code and want to clean up squash commits before PRing, and so want to quickly fixup these commits without having to manually edit descriptions

  1 Copy link to this comment
• 19 Dec, '23
  Joey Kelroy System

  "add fix "f" mode in interactive rebase window" (suggested by Nathanael Feßenbecker on 2023-04-20), including upvotes (4) and comments (1), was merged into this suggestion.

  1 Copy link to this comment
• 19 Dec, '23
  Joey Kelroy System

  "Add 'break' option in interactive rebase" (suggested by Jack on 2023-12-15), including upvotes (1) and comments (0), was merged into this suggestion.

  1 Copy link to this comment
• 03 Jan, '24
  Joey Kelroy System

  "Enable edits to author information for past commits" (suggested by <Hidden> on 2023-12-29), including upvotes (1) and comments (0), was merged into this suggestion.

  2 Copy link to this comment
• 21 Mar, '24
  Dmitry

  Regarding interactive rebase, I'm as software engineer and a user want to see an interactive rebase item in popup window (while dragging a feature branch on main) all the time even if rebasing not possible or not follow-up Git Kraken requirements:
  
  1. No merge commits are present on the branch you’re rebasing
  2. The 2 branches share a common ancestor
  3. Neither branch has the repo’s initial commit
  4. You are not attempting to rebase a parent branch onto a child (like master into a feature branch)
  
  I understand Git Kraken has requirements to hide interactive rebase, but
  my opinion user should know what's happens and not to hide interactive rebase from the user.
  
  Ok, you can show a warning message or something like this but it should be reasonable and not just 'Defense against stupidity'

  1 Copy link to this comment
• 05 Jun, '24
  David Merged

  When i do a interactive rebase, i would like to choose the fixup mode instead of having to use the squash mode and after having to editing the commit message to remove the undesired commit message. If i have multiple commit to fixup, i use vscode interactive rebase editor (and i think it use gitlens for that part, and gitlens is not own by gitkraken so...seem weird that it don't support that option)

  1 Copy link to this comment
• 07 Jun, '24
  Joey Kelroy System

  "Add fixup mode in interactive rebase" (suggested by <Hidden> on 2024-06-05), including upvotes (1) and comments (0), was merged into this suggestion.

  1 Copy link to this comment
• 13 Sep, '24
  Jeff

  I asked to add "edit' a few years ago - supposedly on the to do list. Still waiting

  2 Copy link to this comment
• 30 Oct, '25
  Andre Greeff

  I was just looking at the "GitKraken Desktop Roadmap" and I came to a sudden realisation.... the GitKraken team care more about AI than they do about the devs that use their product. apparently "Advanced AI Workflows" and "Additional AI Capabilities" are more important in their Git client than "Support more interactive rebase commands".
  
  now that this has become abundantly clear to me, I'm no longer on the fence about whether or not to keep my GitKraken subscription going. farewell boys and girls, enjoy the AI slop in your Git history. I'm out.

  1 Copy link to this comment
• 12 Feb
  Stefan

  2026 ... and still nothing :/

  3 Copy link to this comment
• 13 Mar
  Pascal

  This would be much preferred over any additional AI features. I have to keep switching to other tools for imo basic workflows.

  Copy link to this comment