From 93c854610eefd46ea976a1e72309c3bba8c31cb2 Mon Sep 17 00:00:00 2001 From: Pantelis <85220850+Pantelis-Santorinios@users.noreply.github.com> Date: Fri, 20 Dec 2024 12:04:05 +0100 Subject: [PATCH] Update environment-example.md (#53684) Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com> --- data/reusables/actions/environment-example.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/actions/environment-example.md b/data/reusables/actions/environment-example.md index eb02d228267f..f7c5522142a9 100644 --- a/data/reusables/actions/environment-example.md +++ b/data/reusables/actions/environment-example.md @@ -21,7 +21,7 @@ jobs: When the above workflow runs, the `deployment` job will be subject to any rules configured for the `production` environment. For example, if the environment requires reviewers, the job will pause until one of the reviewers approves the job. -You can also specify a URL for the environment. The specified URL will appear on the deployments page for the repository (accessed by clicking **Environments** on the home page of your repository) and in the visualization graph for the workflow run. If a pull request triggered the workflow, the URL is also displayed as a **View deployment** button in the pull request timeline. +You can also specify a URL for the environment. The specified URL will appear on the deployments page for the repository (accessed by clicking **Environments** on the home page of your repository) and in the visualization graph for the workflow run. If a pull request triggered the workflow, the URL is also displayed as a **View deployment** button in the pull request timeline. When using the "Require deployments to succeed before merging" rule, only the `name` specified is being checked even if a URL has also been specified. See [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-deployments-to-succeed-before-merging). ```yaml name: Deployment