Lines Matching +full:pull +full:- +full:requests

3 > Stability: 1 - Experimental
5 _tl;dr: You can land pull requests by adding the `commit-queue` label to it._
9 land pull requests by adding the `commit-queue` label to a PR. All
10 checks will run via node-core-utils, and if the pull request is ready to land,
18 From a high-level, the Commit Queue works as follow:
20 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
23    1. Check if the PR also has a `request-ci` label (if it has, skip this PR
27    3. Remove the `commit-queue` label
28    4. Run `git node land <pr> --oneCommitMax`
31       2. Add `commit-queue-failed` label to the PR
40 To make the Commit Queue squash all the commits of a pull request into the
41 first one, add the `commit-queue-squash` label.
42 To make the Commit Queue land a pull request containing several commits, add the
43 `commit-queue-rebase` label. When using this option, make sure
44 that all commits are self-contained, meaning every commit should pass all tests.
49 work for more complex pull requests. These are the currently known limitations
52 1. All commits in a pull request must either be following commit message
53 …guidelines or be a valid [`fixup!`](https://git-scm.com/docs/git-commit#Documentation/git-commit.t…
54 …will be correctly handled by the [`--autosquash`](https://git-scm.com/docs/git-rebase#Documentatio…
62 The [action](../../.github/workflows/commit-queue.yml) will run on scheduler
67 Using the scheduler is preferable over using pull\_request\_target for two
70 1. if two Commit Queue Actions execution overlap, there's a high-risk that
75    of a pull request, and it will run the Action version present on that
79 `node-core-utils` is configured with a personal token and
81 [@nodejs-github-bot](https://github.com/nodejs/github-bot).
82 `octokit/graphql-action` is used to fetch all pull requests with the
83 `commit-queue` label. The output is a JSON payload, so `jq` is used to turn
85 [`commit-queue.sh`](../../tools/actions/commit-queue.sh).
91 `commit-queue.sh` receives the following positional arguments:
96 4. Every positional argument starting at this one will be a pull request ID of
97    a pull request with commit-queue set.
99 The script will iterate over the pull requests. `ncu-ci` is used to check if
101 the PR is waiting for CI to start (`request-ci` label). The PR is skipped if CI
105 The script removes the `commit-queue` label. It then runs `git node land`,
107 `git node land --abort` is run, and then a `commit-queue-failed` label is added
124 Revert Queue as a follow-up.