It's to figure out which coworker wrote the specific line or ruined the project, so you can blame them :)
Answer from XRay on Stack OverflowGitHub
docs.github.com › en › repositories › working-with-files › using-files › viewing-and-understanding-files
Viewing and understanding files - GitHub Docs
Above the file content, click Blame. This view gives you a line-by-line revision history, with the code in a file separated by commit.
Top answer 1 of 6
448
It's to figure out which coworker wrote the specific line or ruined the project, so you can blame them :)
2 of 6
377
From git-blame:
Annotates each line in the given file with information from the revision which last modified the line. Optionally, start annotating from the given revision.
When specified one or more times, -L restricts annotation to the requested lines.
Example:
johndoe@server.com:~# git blame .htaccess
...
^e1fb2d7 (John Doe 2015-07-03 06:30:25 -0300 4) allow from all
^72fgsdl (Arthur King 2015-07-03 06:34:12 -0300 5)
^e1fb2d7 (John Doe 2015-07-03 06:30:25 -0300 6) <IfModule mod_rewrite.c>
^72fgsdl (Arthur King 2015-07-03 06:34:12 -0300 7) RewriteEngine On
...
Please note that git blame does not show the per-line modifications history in the chronological sense.
It only shows who was the last person to have changed a line in a document up to the last commit in HEAD.
That is to say that in order to see the full history/log of a document line, you would need to run a git blame path/to/file for each commit in your git log.
New to GitHub. How does the Blame feature work? 🤔
You see a shit piece of code, blame tells you who last modified it More on reddit.com
65
297
May 1, 2024Add 'gh blame <path>' command to open blame view on GitHub
Describe the feature or problem you’d like to solve It would be nice to be able to use gh to open the "Blame" view for a file on GitHub from the command line. Proposed solution Using git ... More on github.com
2
October 26, 2020Feature: I wish there could be a 'blame' view for files
Describe the feature or problem you’d like to solve I wish there could be a 'blame' view files like in the portal Proposed solution With this function it is possible to discover changes of ... More on github.com
3
January 20, 2022Support --ignore-revs-file for blame view to support automated code formatters
The blame view of the repository will then be loaded with the --ignore-revs-file parameter and ignores the specified revisions. ... There was an error while loading. Please reload this page. Something went wrong. There was an error while loading. Please reload this page. ... Linking the 1-year-old github ... More on github.com
24
586
Videos
00:45
git: blame #coding #git #gittutorial #github - YouTube
09:13
Quickly Find Who Made The Code Change | Git Blame Explained - YouTube
how I use git blame (beginner - intermediate) anthony ...
04:58
Git Blame: Uncover Code History & Find Who Changed What! - YouTube
00:39
"git blame" - See a File's History (Who Changed What Line & When) ...
00:59
Going Back in Time with Git Blame and Annotate in Visual Studio ...
Git
git-scm.com › docs › git-blame
Git - git-blame Documentation
This makes it possible to track when a code snippet was added to a file, moved or copied between files, and eventually deleted or replaced. It works by searching for a text string in the diff. A small example of the pickaxe interface that searches for blame_usage:
Sara Ford's Blog
saraford.net › 2017 › 02 › 28 › how-to-use-blame-on-github-to-find-the-commit-that-changed-that-line-or-block-of-code-059
How to use Blame on GitHub to find the commit that changed that line or block of code – 059
February 28, 2017 - Clicking on the View blame prior to this change now shows you the file before the “added close button” commit was added. Why this commit? Because this “added close button” commit was the last time line #3 was changed after the “appears in tray” commit.
Reddit
reddit.com › r/github › new to github. how does the blame feature work? 🤔
r/github on Reddit: New to GitHub. How does the Blame feature work? 🤔
May 1, 2024 - The Blame feature in GitHub helps track changes in a file, showing who last modified each line, offering insights into code history and accountability."
GitHub
docs.github.com › en › enterprise-server@3.10 › repositories › working-with-files › using-files › viewing-and-understanding-files
Viewing and understanding files - GitHub Enterprise Server 3.10 Docs
In the upper-right corner of the file view, click Blame to open the blame view.
GitHub
github.com › cli › cli › issues › 2296
Add 'gh blame <path>' command to open blame view on GitHub · Issue #2296 · cli/cli
October 26, 2020 - $ gh blame path/to/file # opens https://github.com/$owner/$repo/blame/$current_branch/path/to/file $ gh blame -L 202,210 path/to/file # opens https://github.com/$owner/$repo/blame/$current_branch/path/to/file#L202-L210 $ gh blame $revision path/to/file # opens https://github.com/$owner/$repo/blame/$revision/path/to/file
Author cli
GitHub
github.com › desktop › desktop › issues › 13708
Feature: I wish there could be a 'blame' view for files · Issue #13708 · desktop/desktop
January 20, 2022 - Describe the feature or problem you’d like to solve I wish there could be a 'blame' view files like in the portal Proposed solution With this function it is possible to discover changes of certain lines of code from the perspective of th...
Author desktop
Atlassian
atlassian.com › git › tutorials › inspecting a repository › git blame
Git blame | Atlassian Git Tutorial
The git blame command is used to examine the contents of a file line by line and see when each line was last modified and who the author of the modifications was. The output format of git blame can be altered with various command line options.
GitHub
docs.github.com › en › enterprise-server@3.13 › repositories › working-with-files › using-files › viewing-and-understanding-files
Viewing and understanding files - GitHub Enterprise Server 3.13 Docs
Above the file content, click Blame. This view gives you a line-by-line revision history, with the code in a file separated by commit.
GeeksforGeeks
geeksforgeeks.org › git › how-to-use-git-blame
Git Blame - GeeksforGeeks
May 6, 2026 - The output of the git blame command ... GitHub, Bitbucket, GitLab offer GUI displays for git blame, which gives a clear display of modification history in a file....
GoLinuxCloud
golinuxcloud.com › home › devops › git › git blame command in git: syntax, options & practical examples
git blame Command in Git: Syntax, Options & Practical Examples | GoLinuxCloud
March 15, 2026 - Navigate to a file in a GitHub repository and click the Blame button at the top of the file view.
Jojozhuang
jojozhuang.github.io › tutorial › tracking-changes-with-blame-view-on-github
Tracking Changes with Blame View on GitHub @ https://jojozhuang.github.io
September 1, 2018 - View entire change history of a file on GitHub. Most source-control systems allow users to view files in annotated or blame mode, in which each line or block of lines is identified by the revision and the user who last modified it.
DataCamp
datacamp.com › tutorial › git-blame
Git Blame Explained: How to Trace Code History and Collaborate Smarter | DataCamp
March 26, 2025 - You can learn more in our Git and GitHub tutorial, which serves as a beginner's guide, explaining the workings of Git version control and highlighting its crucial role in data science projects. ... This command annotates each line with the last commit that modified it, including author, timestamp, and commit hash. Here’s an example: $ git blame example.py derrickmwiti@Derricks-MacBook-Pro remixer % git blame src/components/ContentGenerator.vue ^28203e0 (Derrick Mwiti 2025-03-10 17:48:31 +0300 1) <template> ^28203e0 (Derrick Mwiti 2025-03-10 17:48:31 +0300 2) <div class="content-generator"> ^
GitHub
github.blog › home › changelogs › ignore commits in the blame view (beta)
Ignore commits in the blame view (Beta) - GitHub Changelog
March 22, 2025 - It's now possible to ignore revisions in the blame view using a .git-blame-ignore-revs file in the root of your repository. For more information, see "Ignore commits in the blame view". GitHub Enterprise Server 3.21 is now generally available
CloudBees
cloudbees.com › blog › git-blame-explained
Git Blame Explained With Examples: Who Touched the Code?
October 21, 2021 - One such extension is the appropriately named Git Blame. Upon installing and activating it, VS Code will display, in the status bar, who last touched each line of code: ... That information changes as you navigate through the lines of the file. If you click on the label showing who last touched the given line of code, a pop-up will appear, providing more context for the change: ... Finally, clicking on View will take you to GitHub, to the specified commit’s page.
PhoenixNAP
phoenixnap.com › home › kb › devops and development › git blame: view file modifications line-by-line
git blame: View File Modifications Line-by-Line | phoenixNAP KB
June 3, 2025 - GitHub Public Code Repositories ... May 28, 2025 · Topics: git · The git blame command is a Git tool that allows users to see who last modified each line of a file and when....
GitHub
github.blog › home › news & insights › product › navigate file history faster with improved blame view
Navigate file history faster with improved blame view - The GitHub Blog
December 6, 2019 - Whether you’re debugging a regression or trying to understand how some code came to have its current shape, you’ll often want to see what a file looked like before a particular change. With improved blame view, you can easily see how any portion of your file has evolved over time without viewing the file’s full history. Check out the GitHub Help documentation for more information on using git blame to trace the changes in a file.
