Account Info
You can edit your account-level information by navigating to the settings page in the top bar (1). The first section ("Account") lets you edit general information about your account.
  • The account owner can change the name of the account (2)
  • The account owner can upload a new avatar by clicking on the existing one
  • Professional plan account holders can edit the domain name (3).
  • You can use the authentication token (4) to access the Release API.
Account Settings Example

Account settings

The second section ("Account settings") lets you edit account-level settings for your environments. You can configure properties such as when stale environments are destroyed or recreated, and how public access to your ephemeral environments works.
Ephemeral Environment Settings
  • Create ephemeral environments on Pull Requests: This creates a new ephemeral environment for each new pull request made on your integrated GitHub repositories. We recommend leaving this on so your team and view preview environments for each proposed change to your code base.
  • Recreate pull request ephemeral environments on Push: If your environments are set to expire, you can recreate them when new changes are pushed to a branch. When this setting is on, Release will check for related expired environments for each change pushed. If it finds a match, it will recreate the environment with the latest code changes.
  • Create ephemeral environments for users who don't have Release accounts: This affects users who open PRs to your GitHub repository but don't have Release accounts. If you turn this on, Release will create ephemeral environments for them even if they do not have their own Release account.
  • Destroy ephemeral environments after no activity: If your team opens a high volume of Pull Requests and your cluster is filling up quickly, then it's a good idea to destroy your ephemeral environments as they become stale. If you switch this feature on, then you can determine how long your ephemeral environments will stay alive. If you have a low volume of Pull Requests, then you could leave this off and manually clean up environments as they are no longer needed. If you need an old ephemeral environment in Release that has expired, you can easily re-create it by closing the stale Pull Request re-opening it, or by turning on the Recreate feature described above.
  • Enable unauthenticated environments page: In some cases, it is useful for non-technical staff to access preview environments. For example, your Product Managers, UI/UX designers, and other managerial staff want to check out new changes and offer design feedback or approval. Turning on this feature allows your ephemeral environments to be viewed publicly utilizing a <magic_string> slug that only your team knows about, which you can edit and save.

GitHub settings

If you've integrated your Release account with GitHub, you'll see settings a section on how Release should post information automatically back to GitHub.
Account Settings Example
  • Send comments from Release to GitHub PR's: This will make Release automatically comment on a GitHub pull request with a link to the running environment for that PR. More info here.
  • Send status updates from Release to Github PR's: This integrates with GitHub's status check features to push information about the PR status and any checks from Release to GitHub. More info here.
  • Send deployment updates from Release to Github PR's: This integrates with GitHub's deployment features to push information from Release to GitHub. More info here.
  • Create Environments by applying labels to Github PR's: This integrates with GitHub's labeling features so that you can create environments in Release by adding labels to PRs in GitHub. More info here.