Code workflows
Blame and File History
Blame overlays each line in a file with the commit and author that last changed it. Use it to understand why a line looks the way it does, not just when it was introduced.
Opening blame
From any open file on the Code page, use View → Blame or the toolbar's blame toggle. The file re-renders with a blame gutter on the left, one entry per line showing commit hash (shortened), author, and relative timestamp.
File viewer with blame gutter showing commit hash and author per line
Clicking a blame entry
Click any blame entry to open the full commit in the Diffs and Commits view: message, author, changed files, expandable per-file diffs. Handy for stepping through the history of a suspicious line.
Walking back through history
From the commit view you can jump to the commit's parent and re-blame the file at that revision. Repeat to trace a line back as far as you need.
Related
- The Code page — where you open files in the first place.
- Diffs and Commits — the commit view you jump to from blame.
- The Activity page — the broader project-level activity feed.
