> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/guides/operations-guide/gitops/codeowner-reviewers.md).
# CODEOWNER Reviewers
* People with admin or owner permissions can set up a CODEOWNERS file in a repository.
* The people you choose as code owners must have write permissions for the repository.
* When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership.
* For every branch there will be a **CODEOWNER file.** Only they can able to write the code and able to merge the pull requests.
### Create CODEOWNER file:
* Go to any of your branch(DIGIT branch created previously) in a repository and click on new file and name it as **CODEOWNERS**
* Click on "Create a **new branch** for this commit and start a pull request" and click on **propose new file**
* Next click on **Create pull request** and then **Merge pull request** and **confirm merge.**
* Add the GitHub Id's of all the team or people whom you want to add.
---
# 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.digit.org/platform/guides/operations-guide/gitops/codeowner-reviewers.md?ask=&goal=
```
`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.