Skip to main content
We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation.
 
2022-11-28 (latest)

 

Viewing a file

In this article

You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.

Viewing or copying the raw file content

With the raw view, you can view or copy the raw content of a file without any styling.

  1. On GitHub.com, navigate to the main page of the repository.
  2. Click the file that you want to view.
  3. In the upper-right corner of the file view, click Raw. Screenshot of the Raw button in the file header
  4. Optionally, to copy the raw file content, in the upper-right corner of the file view, click .

Viewing the line-by-line revision history for a file

With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking . Each time you click , you'll see the previous revision information for that line, including who committed the change and when.

Git blame view

In a file or pull request, you can also use the menu to view Git blame for a selected line or range of lines.

Kebab menu with option to view Git blame for a selected line

Tip: On the command line, you can also use git blame to view the revision history of lines within a file. For more information, see Git's git blame documentation.

  1. On GitHub.com, navigate to the main page of the repository.
  2. Click to open the file whose line history you want to view.
  3. In the upper-right corner of the file view, click Blame to open the blame view. Blame button
  4. To see earlier revisions of a specific line, or reblame, click until you've found the changes you're interested in viewing. Prior blame button

Ignore commits in the blame view

All revisions specified in the .git-blame-ignore-revs file, which must be in the root directory of your repository, are hidden from the blame view using Git's git blame --ignore-revs-file configuration setting. For more information, see git blame --ignore-revs-file in the Git documentation.

  1. In the root directory of your repository, create a file named .git-blame-ignore-revs.

  2. Add the commit hashes you want to exclude from the blame view to that file. We recommend the file to be structured as follows, including comments:

    # .git-blame-ignore-revs
# Removed semi-colons from the entire codebase
a8940f7fbddf7fad9d7d50014d4e8d46baf30592
# Converted all JavaScript to TypeScript
69d029cec8337c616552756310748c4a507bd75a

  3. Commit and push the changes.

Now when you visit the blame view, the listed revisions will not be included in the blame. You'll see an Ignoring revisions in .git-blame-ignore-revs banner indicating that some commits may be hidden:

Screenshot of a banner on the blame view linking to the .git-blame-ignore-revs file

This can be useful when a few commits make extensive changes to your code. You can use the file when running git blame locally as well:

git blame --ignore-revs-file .git-blame-ignore-revs

You can also configure your local git so it always ignores the revs in that file:

git config blame.ignoreRevsFile .git-blame-ignore-revs

Bypassing .git-blame-ignore-revs in the blame view

If the blame view for a file shows Ignoring revisions in .git-blame-ignore-revs, you can still bypass .git-blame-ignore-revs and see the normal blame view. In the URL, append a ~ to the SHA and the Ignoring revisions in .git-blame-ignore-revs will disappear.