> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/definitions/frequently-asked-questions/tracking-squashed-commits.md). # Tracking squashed commits GitHub allows you to "squash" commits before merging a pull request. Swarmia supports this workflow. It's possible to [squash commits](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges#merge-message-for-a-squash-merge) when merging a pull request to keep the commit history clean – your individual commits will be replaced with one commit for the whole pull request. It makes it slightly easier to use commands like *git blame* to see which feature contributed to a change, but on the other hand it loses some detail about why a specific change was made. It's mostly a matter of personal preference, and we see teams deciding either way. Squashing commits might cause issues with some other analytics tools because you're losing some detail from the history of a pull request, as it now looks like it was a single commit. In other tools this might mess up calculating things like cycle times. Swarmia will keep the history available in the context of the pull request. This way we'll report cycle time correctly, and you'll see the detailed work in views like Work Log. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.swarmia.com/definitions/frequently-asked-questions/tracking-squashed-commits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.