From d9955ab2a2d16e59ce5e7aade9b04f397df9635b Mon Sep 17 00:00:00 2001 From: Brady Holt Date: Wed, 3 Feb 2021 09:54:03 -0700 Subject: [PATCH] Clarify inactive status made to same environment name (#2430) --- content/rest/reference/repos.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rest/reference/repos.md b/content/rest/reference/repos.md index 67a2f1ffa605..b30002c9f8c3 100644 --- a/content/rest/reference/repos.md +++ b/content/rest/reference/repos.md @@ -144,7 +144,7 @@ Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth- ### Inactive deployments -When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. +When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository to the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. You can communicate that a transient environment no longer exists by setting its `state` to `inactive`. Setting the `state` to `inactive` shows the deployment as `destroyed` in {% data variables.product.prodname_dotcom %} and removes access to it.