> 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/monitors/code-and-repository-monitors/how-to-resolve-sprinto-check-for-classifying-code-repositories.md).

# How to resolve Sprinto check for classifying code repositories

### About

Sprinto Check: Code Repo Classification Reminder

This Sprinto check acts as a prompt to classify code repositories retrieved from your integrated service provider on Sprinto. The check activates for any code repository lacking classification as either "Production" or "Nonproduction.”

### Purpose

Tracking your code repositories is a critical aspect of maintaining compliance. This practice enables continuous monitoring of code changes, ensuring that any modifications align with regulatory requirements and internal policies. Additionally, tracking code repositories helps create an audit trail for code changes. This trail is essential for compliance, showing that your organization follows established code development and deployment procedures. The collected evidence from these controls are submitted in the compliance audit of your desired framework.

### How to Resolve

To address this check, classify all code repositories fetched from your integrated services under Sprinto's Change Management section. You can classify the code repositories as either "Production" or "Non-production." Compliance controls are applied only to code repositories classified as "Production."

Once the code repository is classified, the assigned check status is updated to "Passing." For detailed instructions, refer to[ How to Classify Code Repositories](https://sprinto.freshdesk.com/support/solutions/articles/72000607766-how-to-classify-code-repositories-).

If you require assistance with Sprinto checks, please contact[ Sprinto Support](https://www.notion.so/b8f884f908c44e5e9b01e1484486fcfa?pvs=21).


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.sprinto.com/monitors/code-and-repository-monitors/how-to-resolve-sprinto-check-for-classifying-code-repositories.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.