> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/git-based-source-control/additional-features/issues/labels.md).
# Labels
Labels are used to organize and categorize issues, pull requests, and other items in a repository. You can apply Labels for a variety of purposes, such as indicating the priority of an issue or pull request, marking items that need attention from a particular team or person, or categorizing issues by type or status. For example, you might use labels like "bug", "enhancement", "duplicate", "question", "help wanted", "wontfix" and so on.
Labels for a repository can be access via the Issues tab, in the Labels section. Copia provides a default set of Labels at the Org level (which can be modified) which can be seen at the bottom of the window, and customers can also add/delete additional custom labels at the repository level seen at the top of the window.
To add a new repository label, use the New Label button.
To modify the Organization level labels, use the [Organization Settings](/docs/git-based-source-control/administration/org-settings.md), and select the Labels section. These labels are applied to any new repository that is created.
---
# 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.copia.io/docs/git-based-source-control/additional-features/issues/labels.md?ask=&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.
