> 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.md).

# Repositories

See how to manage your repositories.

### Manage your repositories

1. Click **Repository Settings** on the left side menu.
2. Go to the **Repositories** tab.

In this view, you will find all of your connected repositories along with the details:

* Name - The name of the repository.
* Automations - The automation rules that are triggered anytime you push code, enabling you to prevent risks from entering your codebase and automate notifications and warnings.
* Use case - The use case assigned to your repository, enabling you to get accurate license risk metrics.
* Repository ID - The ID of your repository.
* Integrations - Indicates how this repository was integrated.
* GitHub App scanning - If you have the Fortify SCA GitHub App installed and the repository is tracked, you can enable or disable scanning through it here. If you want to create pull requests, but have Fortify SCA scanning set up in another CI system, you can make use of this function.
* Include hardware dependencies - If you enable this function, Fortify SCA will scan for vulnerabilities related to hardware components, such as Spectre and Meltdown.

### **Delete a depository**

If you decide you no longer want to see data from a specific repository you might want to delete it from the list to clean up your data. To do so, click the **trashcan icon** on the far-right column.

### Export repository table data

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*](https://docs.debricked.com/product/administration/repositories/export-table-data.md) *topic.*

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="https://docs.debricked.com/product/administration/repositories/repository-groups.md"><strong>Repository groups</strong></a></td><td></td><td></td><td><a href="https://docs.debricked.com/product/administration/repositories/repository-groups.md">Repository groups</a></td></tr><tr><td><a href="https://docs.debricked.com/product/administration/repositories/upload-a-dependency-file-manually.md"><strong>Manually upload a dependency file</strong></a></td><td></td><td></td><td><a href="https://docs.debricked.com/product/administration/repositories/upload-a-dependency-file-manually.md">Manually upload a dependency file</a></td></tr><tr><td><a href="https://docs.debricked.com/product/administration/repositories/manage-your-commits.md"><strong>Manage your commits</strong></a></td><td></td><td></td><td><a href="https://docs.debricked.com/product/administration/repositories/manage-your-commits.md">Manage your commits</a></td></tr></tbody></table>


---

# 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.md?ask=<question>&goal=<user_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.
