# Tracking squashed commits 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: 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://help.swarmia.com/definitions/frequently-asked-questions/tracking-squashed-commits.md?ask= ``` 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.