# 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="/files/xCEqchn3S9Es9HnRZGzB" 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="/files/rnapPcAUHwqfXmXhRsPl" 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="/files/xFtxfqK4mnOtlgFlY7K5" 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="/files/026a9SusSgI9l6ZtvKnU" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://johnoraw.gitbook.io/iac-version-control/github/the-basics/logs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.