Skip to content

Commit 656bf7d

Browse files
doc: update commit-queue documentation
update the commit-queue contributing documentation by: - removing the references of the feature being experimental - clarifying that it applies to mergeable pull requests PR-URL: #58275 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Chengzhong Wu <[email protected]>
1 parent e8c06a5 commit 656bf7d

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

doc/contributing/commit-queue.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,8 @@
11
# Commit queue
22

3-
> Stability: 1 - Experimental
4-
53
_tl;dr: You can land pull requests by adding the `commit-queue` label to it._
64

7-
Commit Queue is an experimental feature for the project which simplifies the
5+
Commit Queue is a feature for the project which simplifies the
86
landing process by automating it via GitHub Actions. With it, collaborators can
97
land pull requests by adding the `commit-queue` label to a PR. All
108
checks will run via `@node-core/utils`, and if the pull request is ready to
@@ -18,7 +16,7 @@ implementation details, reasoning for design choices, and current limitations.
1816
From a high-level, the Commit Queue works as follow:
1917

2018
1. Collaborators will add `commit-queue` label to pull requests ready to land
21-
2. Every five minutes the queue will do the following for each pull request
19+
2. Every five minutes the queue will do the following for each mergeable pull request
2220
with the label:
2321
1. Check if the PR also has a `request-ci` label (if it has, skip this PR
2422
since it's pending a CI run)

0 commit comments

Comments
 (0)