Edit your account-level information by clicking the Settings icon in the top bar (1) to navigate to the Settings page.
Edit general information about your account in the "Account" section.
- 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).
Account Settings Example
Edit account-level settings for your environment in the "Account settings" section. 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: If this setting is on, Release will create a new ephemeral environment for each new pull request made on your integrated GitHub repositories. We recommend leaving this on so your team can view preview environments for each proposed change to your code base. This can be overridden at the app level as needed.
- 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: If you have users who will open PRs to your GitHub repository but don't have Release accounts, turn this setting on so that Release can create an ephemeral environment for them.
- 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. Switch this feature on to specify how long your ephemeral environments will stay alive. If you have a low volume of pull requests, then you can leave this off and manually clean up environments as they are no longer needed. If you need an old ephemeral environment that has expired, you can easily re-create it by closing the stale pull request and 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 may want to check out new changes and offer design feedback or approval. Turn this feature on to allow your ephemeral environments to be viewed publicly using a
<magic_string>slug that only your team knows about. You can edit and save your team's slug.
- Enable GitOps: GitOps is a framework for using your git repository to manage your infrastructure and app configuration files. More about GitOps. Contact [email protected] to enable GitOps for your account.
If you've integrated your Release account with GitHub, the GitHub Settings section allows you to set how Release automatically posts information back to GitHub.
Account Settings Example
- Send comments from Release to GitHub PRs: Release will 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 PRs: This setting 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 PRs: This setting integrates with GitHub's deployment features to push information from Release to GitHub. More info here.
- Create Environments by applying labels to Github PRs: This setting integrates with GitHub's labeling features so that you can create environments in Release by adding labels to PRs in GitHub. More info here. These labels can be overridden by the application settings.