๐Ÿ“ Git & GitHub

History, Diffs, and Web Commits on GitHub

P
Author
PyLand Team
๐Ÿ“…
Published
16.07.2026
โฑ๏ธ
Reading time
2 min
๐Ÿ‘๏ธ
Views
311
๐ŸŒฑ
Level
Beginner

GitHub lets you read repository history, inspect individual commit diffs, view the history of one file, and create a small commit directly in the browser.


Repository commit history

  1. Open the repository on GitHub.
  2. Go to Code.
  3. Above the file list, click the commits link next to the clock icon.
  4. Find a commit by its message.

The list shows the author, date, message, and short commit identifier.

An individual commit page

Click a commit message. GitHub shows:

  • changed files;
  • added and removed line counts;
  • removed lines in red;
  • added lines in green;
  • a permanent URL for that commit.

You can share the address-bar URL with a teammate. It points to that exact history entry.

History of one file

  1. Open a file from Code.
  2. Click History above the file content.
  3. GitHub shows commits that changed that file.
  4. Open any commit and inspect its diff.

File history can be shorter than repository history because unrelated commits are omitted. GitHub may also simplify complex histories. Return to the full Commits page if an expected commit is missing.

Make a small edit on GitHub

  1. Open the file.
  2. Click the pencil icon Edit this file.
  3. Change the text.
  4. Use Preview for Markdown.
  5. Click Commit changes….
  6. Enter a short, meaningful message.
  7. Choose where to create the commit and confirm.

The commit now exists on GitHub, but GitHub Desktop still needs to receive it.

Pull the web commit into GitHub Desktop

  1. Open the repository in GitHub Desktop.
  2. Confirm Changes is empty.
  3. Click Fetch origin to check GitHub for new commits.
  4. Click Pull origin to download them and update local files.
  5. Open History and find the web commit.
  6. Compare its diff with the browser view.

Safe viewing versus changes

  • Opening commits, History, and diffs is read-only.
  • Fetch checks remote history without changing working files.
  • Pull updates the local branch with discovered commits.
  • Edit this file changes content only after Commit changes is confirmed.

Checklist

  • I can open the repository Commits page.
  • I can read an individual commit diff.
  • I can copy a permanent commit URL.
  • I can open one file’s History.
  • I understand Fetch versus Pull.
  • I can find a web commit in GitHub Desktop.

Your reaction to the article

๐Ÿ’ฌ Comments (0)

๐Ÿ” Sign in to leave a comment
๐Ÿšช Login
๐Ÿ’ญ

No comments yet

Be the first to share your opinion about this article!

๐Ÿ”— Similar

Similar articles

Continue learning with these materials

๐Ÿ“

Undo and Revert in GitHub Desktop: Fix Mistakes Wโ€ฆ

A commit is not a point of no return. GitHub Desktop lets you rebuild a...

๐Ÿ“… 16.07.2026 ๐Ÿ‘๏ธ 357
๐Ÿ“

Your First Git Commit

Your first commit starts with initializing a repository, configuring the author identity, and selecting the...

๐Ÿ“… 30.06.2026 ๐Ÿ‘๏ธ 341
๐Ÿ“

Git Hosting Platforms

GitHub, GitLab, Bitbucket โ€” key differences and recommendations.

๐Ÿ“… 06.05.2026 ๐Ÿ‘๏ธ 554
๐ŸŽ“ Continue learning

Courses that cover this material

Visit the course to apply this material in practice.

Git & GitHub Desktop: Teamwork Without the Pain Open course curriculum