GitKraken Desktop Documentation

Committing Changes

Last updated: May 2025

GitKraken Desktop simplifies the Git commit process by helping you stage, commit, and push your work from a visual interface.


Making a commit

To create a commit, select your Work in Progress (WIP) node to view file changes in the Commit Panel.

The WIP node appears at the top of the Commit Graph when you save file changes.

Select files to stage by clicking them individually or reviewing diffs. To stage all files:

  • Mac: ShiftS
  • Windows/Linux: CtrlShiftS

Type your commit message, then click Commit, or use the shortcut:

  • Mac: + Enter
  • Windows/Linux: Ctrl + Enter

Commit and push

To commit and immediately push changes, stage files and enter a message. Then select the Commit and Push option.

Enable this option to commit and push changes in one step.

The graph updates with your commit. If needed, undo it with:

  • Mac: + Z
  • Windows/Linux: Ctrl + Z

Committing with Co-Authors

To credit co-authors in a commit, add lines to the commit message using the following format:

Co-authored-by: Name One <[email protected]>
Co-authored-by: Name Two <[email protected]>
Use this syntax to attribute co-authors in a commit.

Co-authors appear in the Commit Panel history:

Co-authors are listed with the primary author in the commit history.

Bypass Git hooks

To skip Git hooks for a specific commit, enable the Skip Git hooks checkbox in the Commit Panel.

Warning: Skipping this will bypass all configured Git hooks for the commit action.

Enable this option to bypass Git commit hooks.

Commit Templates

Reading the Commit Template

When you open a repository, GitKraken Desktop checks for a commit template in this order:

  1. The repository’s local .git/config file
  2. Your global .gitconfig
  3. If neither contains a commit.template setting, GitKraken Desktop does not load a template

Creating and Updating the Commit Template

To create or update a commit template, navigate to Preferences Commit.

Set an initial commit message in Preferences > Commit.

If a template is loaded from your local config, GitKraken Desktop saves changes to that file. If no template exists, your changes are saved to a new gkcommittemplate.txt file in your repo’s .git/ directory. GitKraken Desktop also updates the commit.template path in the local config.

This setup lets you maintain a local template without altering your global Git configuration.

Commit Template Options

  • Apply this template to commit messages: Automatically inserts the template in the message editor.
  • Remove comments from commit messages: Omits lines starting with # when applying the template.

Configuring Commit Templates

There are three ways to configure commit templates:

  • Create in GitKraken Desktop — Saves to .git/gkcommittemplate.txt
  • Set a repo-specific template — Use:
    git config commit.template <path_to_template>
  • Set a global template — Use:
    git config --global commit.template <path_to_template>

Note: Editing a global template within GitKraken Desktop causes it to create `gkcommittemplate.txt` locally and point your repository’s config to that file.


Amending Commits

GitKraken Desktop lets you modify the last commit by updating the message, adding new changes, or both.

To include new changes:

  1. Modify files in your working directory.
  2. Stage the changes.
  3. Select Amend the previous commit in the Commit Panel.
Select this option to append changes to the most recent commit.

To update only the message:

  1. Select the most recent commit in the graph.
  2. Click into the message box and revise the text.
Edit your previous commit message directly in the message field.

To resize the commit message field, drag the bottom edge of the editor.

Resize the commit message box as needed.

Use the Update Message button to save changes, or Cancel Amend to discard them.

Note: If you’ve already pushed a commit, amending it will require a force push to update the remote history.


Resetting Commits

Git uses a pointer called HEAD to track your current commit. Resetting updates HEAD to point to a specific commit in your history. GitKraken Desktop offers three reset types:

  • Soft — Moves HEAD to the selected commit and retains staged and working directory changes.
  • Mixed — Moves HEAD, unstages files, but retains working directory changes.
  • Hard — Moves HEAD, unstages files, and discards all changes in your working directory.
Right-click a commit or branch to access reset options.

You can also drag and drop a branch onto another to initiate a reset, or use the left panel for local repository actions.


Reverting Changes

GitKraken Desktop provides an Undo button to reverse recent actions that haven’t been pushed.

Click Undo to revert local actions before they are pushed.

You can also use the Undo shortcut:

  • Mac: + Z
  • Windows/Linux: Ctrl + Z

Reverting Commits

If Undo is not available, you can still reverse changes by creating a revert commit.

Right-click any commit node in the graph and choose Revert Commit. GitKraken Desktop will create a new commit that undoes the changes from the selected commit.

Use the revert option to create a new commit that undoes a previous one.
Have feedback about this article? Did we miss something? Let us know!
On this page