# Repository Settings

## What are the repository settings?

Managers of the organization can update repository settings. As a manager, you can go to repository settings by clicking settings from the bottom left menu and go to detail of the integration that you provided to fetch repositories for example github,

<https://app.iftrue.co/settings> or [https://\[your\_org\_slug\].app.iftrue.co/settings](https://app.iftrue.co/settings)

![](/files/vtDMknpf3dIbY9jAkD4h)

Than navigate to repository settings page

<figure><img src="/files/lsdHJN7ezdrI5hWxihLA" alt=""><figcaption><p>iftrue | repository settings</p></figcaption></figure>

### **Production Branch**

* This tells us which branch you merge when a pull request ready to be deployed. The branch name should be exact match.

For example, most teams use `main` branch as their base branch.

### **Failure Tracking**

Enhance your MTTR and change failure rate tracking with our failure tracking options, crucial for accurate DORA metric assessment. To ensure precise values, we require your input on how failures should be tracked. Choose from two comprehensive options to inform us about your preferred approach for failure tracking:

1. **Pull Request Label**

This choice includes an additional option to select the specific label from your git provider that you utilize to distinguish bug fixes.&#x20;

![](/files/Nfis3yWOCiNxjhTQLUAR)

2. **Pull Request Prefix**

If you opt for this choice, kindly provide us with the prefix you use. Many teams follow conventional commits in their commit and pull request names, such as:

![](/files/iiisg09pPpvviYsWCdi5)

### **Deployment Tracking Options**

1. **Merge to production branch**

   By selecting this option, we'll track deployments when code is merged directly into your production branch. This helps us provide accurate insights into your deployment frequency and streamline your development process.
2. **Merge to custom branch**

   Opt for this option if your team follows a specific workflow where code is merged into a custom branch before being deployed to production.
3. **Pull request with prefix**

   If your team employs a naming convention for pull requests that includes a specific prefix, this option is for you. Inform us about the prefix you use in your pull request titles, and we'll tailor our deployment tracking to match.
4. **Pull request with label**

   For teams that classify pull requests using specific labels, this option is ideal. Let us know which label you assign to your pull requests when they're ready for deployment.
5. **Github Action**

   Opt for this option if you utilize GitHub Actions to manage your deployments. By integrating with your existing workflows, we can seamlessly track deployments triggered by GitHub Actions, providing you with accurate metrics and valuable performance insights.
6. **HTTP Request**

   This endpoint allows you to create a deployment for an organization with specified parameters. Please navigate [this page](/getting-started/basics/repository-settings/deployment-tracking-with-http-request.md) for more information.


---

# 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://docs.iftrue.co/getting-started/basics/repository-settings.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.