> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/app-maker/projects/commits.md).
# Commits
The Commits page lists every commit in a project's managed git repository, with a per-commit diff view — useful for tracing exactly what changed between two builds, or reviewing a single commit before deciding whether it needs a new build.
## Opening Commits
From a project's [Dashboard](/tutorials/app-maker/projects/project-details.md), click **Commits** in the footer of the **Repository** card.
## The Commit List
Each row shows:
* **SHA** — the commit's short hash, with a copy icon for the full hash.
* **Message** — the commit's subject line (hover to see the full message).
* **Author** — the commit author's name (hover to see their email).
* **Commit Date** — when the commit was made.
* **Actions** — opens the commit's detail page.
A branch is preselected for you — `main` if the repository has it, otherwise the first branch alphabetically — so the list has something to show before you touch a filter.
Use the filter icon (top-right of the table) to narrow the list:
* **Branch** — restrict the list to commits on a specific branch.
* **From Tag** / **To Tag** — restrict the list to the commit range between two tags.
{% hint style="warning" %}
The commit history walk has a scan limit. If a filtered range is longer than that limit, a banner above the list warns that the results are incomplete — narrow the tag range to see the rest.
{% endhint %}
The list uses **Prev**/**Next** rather than numbered pages or a total count, since a large range's true total isn't always known up front.
## Commit Detail
Opening a commit shows its message, full SHA, author, and commit date, followed by a diff of every file it changed.
The diff itself is the same viewer used by the [Upgrade Helper](/tutorials/app-maker/developer-tools-and-cli/upgrade-helper.md) — a resizable file tree sidebar (drag its edge to widen it) with lines-added/removed counts, a Split/Unified toggle (opens in Unified), and per-file review actions (copy path, copy anchor link, view raw contents, view full file content in a modal, mark as viewed). All files start expanded, since a commit is usually reviewed as one unit rather than file by file.
**View full file content** opens the file as it stands at that commit — not just the changed lines — in a read-only modal titled with the file's path. The content is syntax-highlighted and carries a copy button, and the modal can be expanded to fill the window for a long file. Binary files and files too large to fetch show a notice in place of the content.
Two states get their own explicit treatment rather than looking like an empty or missing diff:
* **Binary files** show a notice that the file is binary instead of an empty diff panel.
* **Very large commits** — past a size/file-count cap — show a warning banner above the diff, so a capped view never looks like the complete change.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.akinon.com/tutorials/app-maker/projects/commits.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
