GitGlow 2.0 guide

Trace file history and blame

Follow one path through revisions and inspect line attribution.

Reviewed for 2.0Updated September 13, 2026
On this page

What this helps you do

Follow one path through revisions and inspect line attribution.

Find it in GitGlow

Use File history from the diff toolbar, or choose Blame from a supported file view.

Before you start

Free for tracked text files with available history.

Steps

  1. Open a tracked file from Changes or a commit.
  2. Choose File history to see relevant commits, or Blame to inspect line ownership.
  3. Select an attribution to return to its commit in History.

Expected result

The selected file, revision, and commit inspector remain connected.

Controls

File historychanges.file-history

Opens history for the selected path.

Screen
Diff toolbar
Available
Free desktop
Open workflow guide →

Recovery

If the workflow cannot continue

Renamed or deleted paths may require selecting an earlier revision. Binary files do not expose text blame.