IAC - Version Control
GITHUB
GITHUB
  • Background
  • Setting up GitHub
  • Windows
    • Working with a cloned repo
    • Populating a repo from local files
    • Integrate VSCode
  • Linux
    • Using SSH
    • GH Command Line
  • The Basics
    • Forks
    • Logs
    • Undoing Local Changes
  • Larger Projects
    • Setting up a repo
    • Creating my Branch Architecture Locally
    • Creating a Feature Branch
    • Creating my Branch Architecture on GitHub
    • Merging the changes from GitHub on my local machine
    • Merging the changes from my local machine to GitHub
    • Sync the branches in GitHub
  • Finally
Powered by GitBook
On this page
  1. The Basics

Logs

PreviousForksNextUndoing Local Changes

In previous notes we looked at the git log command. We saw that each commit has a long SHA256 code associated with it.

We saw the HEAD keywork, pointing at the most recent commit that the repo has a record of. Instead of using the long SHA256 code, we can just use the keyword HEAD. I can look in detail at the most recent change.

Remember, red for deleted, green for new.

I can see the same information in GitHub, the SHA keys are shortened to the first 7 characters.

If I click on the SHA code, I can view the commit. The information should be consistent with what I saw using git log through the terminal.