> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/reference-documentation/application-settings/github.md).

# GitHub

Create environments in Release with GitHub labels

You can integrate your Release account or application with [GitHub labels](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels) to create an environment in Release when you add a label to a pull request.

Customize the GitHub label you use to create environments at the account level in your [Account Settings](/reference-documentation/account-settings/account-info.md#github-settings) or at the application level in "GitHub Settings".

![](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-fde210c7a560eb9fc8b7d4ec0085acda291b1a4a%2Fgithub.png?alt=media)

{% hint style="warning" %}
**If you set a GitHub label in Application Settings, it will override any label set in your Account Settings for this app.**
{% endhint %}

Add the name of the GitHub label to the "GitHub Label Name" field in the "GitHub Settings" section of your Release Application Settings. Apply the label to a pull request when you want Release to create a new environment for it.

To remove a label set at application level, delete the label's name from the "GitHub Label Name" field and click "Save".


---

# 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.release.com/reference-documentation/application-settings/github.md?ask=<question>&goal=<user_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.