GitGlow 2.0 guide

Use reflog and recovery references

Inspect local movement and preserve pre-operation tips without silently rewriting refs.

Reviewed for 2.0Updated September 13, 2026
On this page

What this helps you do

Inspect local movement and preserve pre-operation tips without silently rewriting refs.

Find it in GitGlow

Open Reflog from History or use a Recovery reference shown by an operation.

Before you start

Reflog is read-only and Free. Pro history edits create recovery refs; reviewing them remains available after expiry.

Steps

  1. Inspect the reflog entry or recovery ref and its target.
  2. Choose Review recovery branch and enter a new branch name.
  3. Review the exact saved ref before creating the branch.

Expected result

A separate local branch points to the reviewed historical object; the current branch does not move.

Controls

Review branchoperation.recovery

Creates a separate branch at the saved recovery ref.

Screen
Operation recovery
Available
Available when a recovery ref exists
Open workflow guide →

Recovery

If the workflow cannot continue

If the name exists, choose another name. Recovery references are narrower than a universal undo.