GitGlow 2.0 guide

Stage changes and compose commits

Build clean commits from whole files, hunks, or supported line selections.

Reviewed for 2.0Updated September 13, 2026
On this page

What this helps you do

Build clean commits from whole files, hunks, or supported line selections.

Find it in GitGlow

Use Changes and the commit composer.

Before you start

File, hunk, line staging, unstaging, and local commits are Free desktop actions.

Steps

  1. Select the exact file, hunk, or consecutive changed lines.
  2. Choose Stage or Unstage and verify the group and counts update.
  3. Write the subject and optional body, then review and confirm the commit.

Expected result

Only reviewed staged content enters the new commit, and successful commits offer follow-up actions without pushing.

Controls

Stage filechanges.stage-file

Stages the selected whole-file state.

Screen
Changes
Available
Free desktop
Open workflow guide →
Stage hunkchanges.stage-hunk

Stages one backend-identified hunk.

Screen
Changes
Available
Free desktop
Open workflow guide →
Stage selected lineschanges.stage-lines

Stages supported consecutive changed lines.

Screen
Changes
Available
Free desktop
Open workflow guide →
Unstagechanges.unstage

Moves selected index content back to working changes.

Screen
Changes
Available
Free desktop
Open workflow guide →

Recovery

If the workflow cannot continue

A stale preview disables apply. Refresh while preserving the commit draft, then review the new identity.