Skip to content

Commit 1e6ab0e

Browse files
PickHubCopilot
PickHub
and
Copilot
authored
Document required deployments for stacked PRs (#64519)
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
1 parent 957f4c5 commit 1e6ab0e

4 files changed

Lines changed: 14 additions & 0 deletions

File tree

‎content/pull-requests/reference/stacked-pull-requests.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,7 @@ The following are all evaluated as if each pull request targets the stack base,
4646
| Required status checks | Evaluated against the stack base. |
4747
| CODEOWNERS | Evaluated from the stack base. Changes to `CODEOWNERS` in a lower pull request, but does not affect pull requests above it. |
4848
| Code scanning workflows | Evaluated against the stack base. |
49+
| Required deployments | Evaluated against the stack base. Deploying a pull request also satisfies this requirement for pull requests below it while the stack has a linear history. |
4950

5051
## {% data variables.product.prodname_actions %}
5152

‎content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -145,6 +145,12 @@ Before you can require a linear commit history, your repository must allow squas
145145

146146
You can require that changes are successfully deployed to specific environments before a branch can be merged. For example, you can use this rule to ensure that changes are successfully deployed to a staging environment before the changes merge to your default branch.
147147

148+
{% ifversion pr-stacks %}
149+
150+
{% data reusables.pull_requests.pr-stack-required-deployments %}
151+
152+
{% endif %}
153+
148154
### Lock branch
149155

150156
Locking a branch will make the branch read-only and ensures that no commits can be made to the branch. Locked branches can also not be deleted.

‎content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,12 @@ You can configure various settings for your merge queue rule.
7777

7878
You can require that changes are successfully deployed to specific environments before a branch can be merged. For example, you can use this rule to ensure that changes are successfully deployed to a staging environment before the changes merge to your default branch.
7979

80+
{% ifversion pr-stacks %}
81+
82+
{% data reusables.pull_requests.pr-stack-required-deployments %}
83+
84+
{% endif %}
85+
8086
## Require signed commits
8187

8288
When you enable required commit signing on a branch, contributors {% ifversion fpt or ghec %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see [AUTOTITLE](/authentication/managing-commit-signature-verification/about-commit-signature-verification).

‎data/reusables/pull_requests/pr-stack-required-deployments.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
For stacked pull requests, deploying a pull request also satisfies this requirement for pull requests below it while the stack has a linear history. See [AUTOTITLE](/pull-requests/reference/stacked-pull-requests#branch-protections-and-required-checks).

0 commit comments

Comments
 (0)