Skip to content

File History โ€‹

Track the complete history of any file across all commits.

Opening File History โ€‹

  1. Press Ctrl+F to open the search & filter panel
  2. Type a filename in the file search field
  3. Click a result to open its history

From the File Browser โ€‹

  1. Click the folder icon (๐Ÿ“) in the file search field
  2. Browse the repository tree
  3. Click any file to open its history

From Staging Panel โ€‹

  1. Right-click any file (staged or unstaged)
  2. Select File history

From Commit Details โ€‹

  1. Click a commit in the graph
  2. Right-click any file in the list
  3. Select File history

The File History Panel โ€‹

Shows all commits that modified the selected file:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ ๐Ÿ“„ src/components/Login.tsx         โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚ feat: add remember me option        โ”‚
โ”‚ John Doe โ€ข 2 hours ago โ€ข a1b2c3d    โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚ fix: resolve validation bug         โ”‚
โ”‚ Jane Smith โ€ข Yesterday โ€ข e4f5g6h    โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚ feat: create login component        โ”‚
โ”‚ John Doe โ€ข Last week โ€ข i7j8k9l      โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Viewing Changes โ€‹

Click any commit in the history to see:

  • What changed in that specific commit
  • The diff for just that file
  • Before/after comparison

Use Cases โ€‹

Understanding Code Evolution โ€‹

See how a function changed over time:

  1. Open file history
  2. Scroll through commits
  3. Click each to see changes

Finding Bug Introduction โ€‹

Identify when a bug was introduced:

  1. Open history for buggy file
  2. Look for suspicious changes
  3. Find the problematic commit

Tracking Authorship โ€‹

See who changed what and when:

  • Each commit shows author
  • Useful for questions and reviews

Recovering Old Code โ€‹

Find how code looked before:

  1. Find relevant commit
  2. View the file at that point
  3. Copy what you need

Scrolling โ€‹

  • Scroll through commit list
  • Older commits at bottom

Clicking โ€‹

  • Click commit to view changes
  • Diff shows that commit's changes

Closing โ€‹

  • Click X button
  • Press Escape

Tips โ€‹

Check the Right File โ€‹

Ensure you're viewing history for the correct path. Renamed files may have separate histories.

Read Commit Messages โ€‹

Good messages explain why changes were made.

If history doesn't explain everything, check files changed in the same commits.

Limitations โ€‹

Renamed Files โ€‹

History may not follow renames automatically. You might see history only from the rename forward.

Deleted Files โ€‹

Cannot open history for deleted files from UI. Use terminal:

bash
git log --all -- path/to/deleted/file

Large Histories โ€‹

Files with many commits may take a moment to load.

Built for developers who love Git but hate complexity. Terms ยท Privacy