> 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/frequently-asked-questions/release-faq.md).

# Release FAQ

## Why wasn't an environment created for my pull request?

Several settings affect whether Release creates environments or builds for a particular pull request, all of which you can find in the Account Settings page.

Click your user icon in the top right, then **Manage Organization**. Click **Settings** next to the account you would like to manage.

If the "Create ephemeral environments on Pull Requests" and "Create Environments by applying labels to Github PR's" settings are both "Off", Release will not create environments automatically on pull request.

If the "Create ephemeral environments on Pull Requests" setting is "Off" and the "Create Environments by applying labels to Github PR's" setting is "On", Release will only create an environment if the label is applied to your pull request. If there is no custom label set, Release will not automatically create an environment.

If the "Create ephemeral environments for users who don't have Release accounts" setting is "Off", Release will not create an environment if the pull request is made by a user who does not have a Release account, regardless of the other settings.


---

# 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/frequently-asked-questions/release-faq.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.