> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/change-management/dashboard-actions/classify-code-repositories.md).

# Classify Code Repositories

### **About:**

The procedure below describes classifying code repositories in the integrated code repository systems. Classifying the code repositories that directly contribute to the service or product is mandatory per the security framework requirement.

### **Prerequisites:**

* Logged in on Sprinto as an administrator.
* Code repositories systems are set up on Sprinto. Refer to [How to Set Up Code Repositories On Sprinto?](/data-library/change-management/dashboard-actions/adding-and-editing-change-management-systems.md).

### **Procedure:**

1. Navigate to **Data Library** > **Change Management**, then click on the code repository system whose repositories you want to classify.
2. Click on **Manage** for the repository you want to classify.

{% hint style="info" %}
By default, repositories tracked from repository systems are not classified. A monitor is activated for all non-classified repositories, and users must classify the repository to pass the check.
{% endhint %}

3. On manage repo page, click on **Classify.**                                                        &#x20;

<figure><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/72056187428/original/5ah24zTLjA1uwr1cadawXrA5hqivSyFgEg.png?1689278170" alt=""><figcaption></figcaption></figure>

4. On manage repo classification page, select one of the following options to classify the selected repository.
   * **Production**: If the stored code on the repository contributes directly to the service or product.
   * **Not Production:** If the stored code on the repository is not directly contributing to the product’s functionality.&#x20;

<figure><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/72056187535/original/SOb3Kn14AL3-qBs438lJ3pf155XZW-03ow.png?1689278207" alt=""><figcaption></figcaption></figure>

5. If you have classified the repository as “Production,” select the branches of the repository to be considered under the CI.                                                              &#x20;

{% hint style="info" %}
CI stands for Continuous Integration branches. These are branches that merge changes and deploy them to production.
{% endhint %}

<figure><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/72056187569/original/c4JHwKQ6-RU2e849Oagavw9BNEydVs1m0g.png?1689278223" alt="" width="563"><figcaption></figcaption></figure>

6. Click on **Save.**

<figure><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/72056187619/original/mhzBQezOUKO8y6u4KD8HcH8ev5OiXT4mcw.png?1689278246" alt="" width="563"><figcaption></figcaption></figure>

### **Result:**

Once a repository has been successfully classified, you can view its classification status and check against the repository in “Passing” status.

<figure><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/72056187671/original/JwSvfVxFw917RbB8oO0zzSDLjCP3TwEZgw.png?1689278262" alt="" width="563"><figcaption></figcaption></figure>


---

# 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:

```
GET https://docs.sprinto.com/data-library/change-management/dashboard-actions/classify-code-repositories.md?ask=<question>
```

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.
