> For the complete documentation index, see [llms.txt](https://johnoraw.gitbook.io/iac-version-control/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://johnoraw.gitbook.io/iac-version-control/github/the-basics/logs.md).

# Logs

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

<figure><img src="https://content.gitbook.com/content/C1tv1gDCmQOVxTprzQP4/blobs/sWDb32xeohQAQ28SOsAs/image.png" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://content.gitbook.com/content/C1tv1gDCmQOVxTprzQP4/blobs/2cqnnTfwiy2ryQmS4glZ/image.png" alt=""><figcaption></figcaption></figure>

Remember, <mark style="color:red;">red</mark> for deleted, <mark style="color:green;">green</mark> for new.

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

<figure><img src="https://content.gitbook.com/content/C1tv1gDCmQOVxTprzQP4/blobs/HM0WmmeI4QvvSSGYIkLW/image.png" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://content.gitbook.com/content/C1tv1gDCmQOVxTprzQP4/blobs/knkzJRy7Yfuf4s0tbDbl/image.png" alt=""><figcaption></figcaption></figure>
