Skip to content

Commit 0afd9ab

Browse files
4wrxbnguyenalex836willsmythe
authored
Clarify merge queue merge limits (#31807)
Co-authored-by: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com> Co-authored-by: Will Smythe <willsmythe@github.com>
1 parent 357cbff commit 0afd9ab

File tree

1 file changed

+7
-1
lines changed
  • content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges

1 file changed

+7
-1
lines changed

content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,13 @@ Once you have enabled the "Require merge queue" setting, you can also access the
7575
- **Status check timeout**: Choose how long the queue should wait for a response from CI before assuming that checks have failed.
7676

7777
-
78-
**Merge limits**: Select the minimum and maximum number of pull requests to merge in a single group (between `1` and `100`), and a timeout after which the queue should stop waiting for more entries and merge with fewer than the minimum number of pull requests. Exactly how many PRs are included in a group depends on a merge queue's settings:
78+
**Merge limits**: Select the minimum and maximum number of pull requests to merge into the base branch at the same time (between `1` and `100`), and a timeout after which the queue should stop waiting for more entries and merge with fewer than the minimum number.
79+
80+
{% note %}
81+
82+
**Note:** Merge limits do not combine `merge_group` **builds**. Merge limits only affect merges to the base branch once one or more `merge_group` has satisfied build checks.
83+
84+
{% endnote %}
7985

8086
| Merge Limit | Use Case |
8187
| ----------- | -------- |

0 commit comments

Comments
 (0)