GitGlow 2.0.5 guide

Edit unpublished history

Amend, cherry-pick, revert, or prepare a bounded rewrite after publication checks.

Reviewed for 2.0Updated September 13, 2026
On this page

What this helps you do

Amend, cherry-pick, revert, or prepare a bounded rewrite after publication checks.

Find it in GitGlow

Open a commit in History and choose an available history action.

Before you start

Pro. Amend and visual rewrite require unpublished work; cherry-pick and revert can enter the shared resolver.

Steps

  1. Select the exact commit or tip action.
  2. Review publication state, cleanliness, affected refs, and the recovery promise.
  3. Confirm the preview once; resolve or abort any resulting operation.

Expected result

GitGlow executes a fixed operation only after state revalidation and records the recovery path.

Controls

Amendhistory.amend

Previews amending the clean unpublished tip.

Screen
History
Available
Pro
Open workflow guide
Cherry-pickhistory.cherry-pick

Previews applying a selected commit.

Screen
History
Available
Pro
Open workflow guide
Reverthistory.revert

Previews a new commit reversing the selection.

Screen
History
Available
Pro
Open workflow guide

Recovery

If the workflow cannot continue

Unknown remote state blocks destructive history edits. Fetch first so publication can be determined.

Practice the Git workflow

Use self-contained local exercises to understand the Git behavior behind these controls.