Last updated: March 2026
Use this page to run interactive rebase in GitKraken Desktop when you need to reorder, combine, rename, or drop commits before sharing or merging a branch. It explains how to start the rebase, what the available actions do, and which branch and history conditions must be met before the workflow is available.
Requirements and limits
- Workflow scope: Rewrite local branch history before sharing or merging
- Required branch condition: Branches must share a common ancestor
- Rebase limitation: Interactive rebase is not available for merge commits
- Source-branch limitation: No merge commits may exist on the source branch
- Initial-commit limitation: Neither branch may include the repository’s initial commit for this workflow
- Tooling limitation: If you start the rebase in GitKraken Desktop, you must complete it there
Quick Start
To start interactive rebase:
- Drag and drop a branch onto a target branch and select Interactive Rebase.
- Or right-click a target branch in the Left Panel and choose Interactive Rebase.
- Or right-click any parent commit in the graph and select the option.
Available commit actions:
- Pick: Keep the commit as-is.
- Reword: Edit the commit message.
- Squash: Combine the commit into its parent commit.
- Drop: Remove the commit from history entirely.
Keyboard shortcuts in the rebase view: P = Pick, S = Squash, R = Reword, D = Drop.
To undo all changes before confirming, click Reset. Interactive rebase requires that branches share a common ancestor and that no merge commits exist on the source branch. If you start the rebase in GitKraken Desktop, you must complete it there.
How to start an interactive rebase
To begin:
- Drag and drop one branch onto another
- Or right-click a target branch and select Interactive Rebase

You can also right-click any parent commit to access the option. Note: Interactive rebase is not available for merge commits.
Interactive rebase requirements
Interactive rebase is available only if:
- The branches share a common ancestor
- No merge commits exist on the source branch
- Neither branch includes the repo’s initial commit
- You’re not trying to rebase a parent onto a child (e.g.,
mainontofeature)
Note: If you start the rebase in GitKraken Desktop, you must complete it there.
What the interactive rebase actions do
How Pick works
Moves the commit onto the target branch as-is.

How Reword works
Opens a modal to edit the commit summary and description.

How Squash works
Combines the selected commit into its parent.

How Drop works
Removes the commit entirely and rewrites the graph.

How shortcuts and Reset work
Use these keyboard shortcuts during rebase:
- P: Pick
- S: Squash
- R: Reword
- D: Drop
To undo all changes during setup, click .
