> For the complete documentation index, see [llms.txt](https://docs.debricked.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.debricked.com/product/administration/repositories/manage-your-commits.md).
# Manage your commits
Learn how to manage commits in your repositories.
After creating several commits or adding a repository with existing commits, it might be important to be able to look back and see the history of the changes. To see a list of all your commits and manage them:
1. Click **Repository Settings** on the left side menu.
2. Go to the **Commits** tab.
3. Click the repository you are interested in.
In this view, you can find a list of all your commits, along with the details:
* Name - The name of the commit.
* Commit Date - The date and time the commit was created.
* Repository - The repository the commit belongs to.
* Branch - The branch the commit was added to.
* Added by - The user by whom the commit was added.
> You can export the filtered and visible data in the table to a CSV file. To do so, click **Export Table** located at the top-right corner of the table. *For more information, refer to the* [*Export table data*](/product/administration/repositories/export-table-data.md) *topic.*
### **Delete a commit**
If you decide you no longer want to see data from a specific repository and remove it, or if you revert a commit on your end, it might be useful to delete a commit from the list to clean up your data. To do so, click the **trashcan** icon on the far-right column.
### **Retention time of commit data**
Unless you delete the commit data manually, non-default branches will be retained for 30 days, while default branches (*main*, *master*) have an unlimited retention period.
Additionally, enterprise users can tag selected commits as a release by adding the flag `--tag-commit-as-release=true` to the `scan` command in Fortify SCA CLI. Storing the commit data indefinitely (they can still be manually removed).
---
# 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://docs.debricked.com/product/administration/repositories/manage-your-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.
