From 9978e7ad5aac505a9798057b976ad1b15bbe2543 Mon Sep 17 00:00:00 2001 From: Dario Piotrowicz Date: Sun, 11 May 2025 12:51:36 +0100 Subject: [PATCH] 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 --- doc/contributing/commit-queue.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/doc/contributing/commit-queue.md b/doc/contributing/commit-queue.md index cece9ea84e94f8..a47b1d84f29a5f 100644 --- a/doc/contributing/commit-queue.md +++ b/doc/contributing/commit-queue.md @@ -1,10 +1,8 @@ # Commit queue -> Stability: 1 - Experimental - _tl;dr: You can land pull requests by adding the `commit-queue` label to it._ -Commit Queue is an experimental feature for the project which simplifies the +Commit Queue is a feature for the project which simplifies the landing process by automating it via GitHub Actions. With it, collaborators can land pull requests by adding the `commit-queue` label to a PR. All 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. From a high-level, the Commit Queue works as follow: 1. Collaborators will add `commit-queue` label to pull requests ready to land -2. Every five minutes the queue will do the following for each pull request +2. Every five minutes the queue will do the following for each mergeable pull request with the label: 1. Check if the PR also has a `request-ci` label (if it has, skip this PR since it's pending a CI run)