Na}{

File Content: `commit-queue.md`

# 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
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 land,
the Action will rebase it and push to `main`.

This document gives an overview of how the Commit Queue works, as well as
implementation details, reasoning for design choices, and current limitations.

## Overview

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
   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)
   2. Check if the last Jenkins CI is finished running (if it is not, skip this
      PR)
   3. Remove the `commit-queue` label
   4. Run `git node land <pr> --oneCommitMax`
   5. If it fails:
      1. Abort `git node land` session
      2. Add `commit-queue-failed` label to the PR
      3. Leave a comment on the PR with the output from `git node land`
      4. Skip next steps, go to next PR in the queue
   6. If it succeeds:
      1. Push the changes to nodejs/node
      2. Leave a comment on the PR with `Landed in ...`
      3. Close the PR
      4. Go to next PR in the queue

To make the Commit Queue squash all the commits of a pull request into the
first one, add the `commit-queue-squash` label.
To make the Commit Queue land a pull request containing several commits, add the
`commit-queue-rebase` label. When using this option, make sure
that all commits are self-contained, meaning every commit should pass all tests.

## Current limitations

The Commit Queue feature is still in early stages, and as such it might not
work for more complex pull requests. These are the currently known limitations
of the commit queue:

1. All commits in a pull request must either be following commit message
   guidelines or be a valid [`fixup!`](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---fixupamendrewordltcommitgt)
   commit that will be correctly handled by the [`--autosquash`](https://git-scm.com/docs/git-rebase#Documentation/git-rebase.txt---autosquash)
   option
2. A CI must've ran and succeeded since the last change on the PR
3. A collaborator must have approved the PR since the last change
4. Only Jenkins CI and GitHub Actions are checked (V8 CI and CITGM are ignored)

## Implementation

The [action](../../.github/workflows/commit-queue.yml) will run on scheduler
events every five minutes. Five minutes is the smallest number accepted by
the scheduler. The scheduler is not guaranteed to run every five minutes, it
might take longer between runs.

Using the scheduler is preferable over using pull\_request\_target for two
reasons:

1. if two Commit Queue Actions execution overlap, there's a high-risk that
   the last one to finish will fail because the local branch will be out of
   sync with the remote after the first Action pushes. `issue_comment` event
   has the same limitation.
2. `pull_request_target` will only run if the Action exists on the base commit
   of a pull request, and it will run the Action version present on that
   commit, meaning we wouldn't be able to use it for already opened PRs
   without rebasing them first.

`node-core-utils` is configured with a personal token and
a Jenkins token from
[@nodejs-github-bot](https://github.com/nodejs/github-bot).
`octokit/graphql-action` is used to fetch all pull requests with the
`commit-queue` label. The output is a JSON payload, so `jq` is used to turn
that into a list of PR ids we can pass as arguments to
[`commit-queue.sh`](../../tools/actions/commit-queue.sh).

> The personal token only needs permission for public repositories and to read
> profiles, we can use the GITHUB\_TOKEN for write operations. Jenkins token is
> required to check CI status.

`commit-queue.sh` receives the following positional arguments:

1. The repository owner
2. The repository name
3. The Action GITHUB\_TOKEN
4. Every positional argument starting at this one will be a pull request ID of
   a pull request with commit-queue set.

The script will iterate over the pull requests. `ncu-ci` is used to check if
the last CI is still pending, and calls to the GitHub API are used to check if
the PR is waiting for CI to start (`request-ci` label). The PR is skipped if CI
is pending. No other CI validation is done here since `git node land` will fail
if the last CI failed.

The script removes the `commit-queue` label. It then runs `git node land`,
forwarding stdout and stderr to a file. If any errors happen,
`git node land --abort` is run, and then a `commit-queue-failed` label is added
to the PR, as well as a comment with the output of `git node land`.

If no errors happen during `git node land`, the script will use the
`GITHUB_TOKEN` to push the changes to `main`, and then will leave a
`Landed in ...` comment in the PR, and then will close it. Iteration continues
until all PRs have done the steps above.

## Reverting broken commits

Reverting broken commits is done manually by collaborators, just like when
commits are landed manually via `git node land`. An easy way to revert is a
good feature for the project, but is not explicitly required for the Commit
Queue to work because the Action lands PRs just like collaborators do today. If
once we start using the Commit Queue we notice that the number of required
reverts increases drastically, we can pause the queue until a Revert Queue is
implemented, but until then we can enable the Commit Queue and then work on a
Revert Queue as a follow-up.

Name	Size	Permission
doc_img	---	0755
adding-new-napi-api.md	2614 bytes	0644
backporting-to-release-lines.md	5856 bytes	0644
building-node-with-ninja.md	1757 bytes	0644
code-of-conduct.md	2175 bytes	0644
collaborator-guide.md	43642 bytes	0644
commit-queue.md	5899 bytes	0644
components-in-core.md	2566 bytes	0644
cpp-style-guide.md	13117 bytes	0644
diagnostic-tooling-support-tiers.md	8181 bytes	0644
feature-request-management.md	3492 bytes	0644
internal-api.md	539 bytes	0644
investigating-native-memory-leaks.md	27720 bytes	0644
issues.md	3392 bytes	0644
maintaining-V8.md	20277 bytes	0644
maintaining-c-ares.md	1673 bytes	0644
maintaining-cjs-module-lexer.md	2259 bytes	0644
maintaining-dependencies.md	4543 bytes	0644
maintaining-http.md	4897 bytes	0644
maintaining-icu.md	8357 bytes	0644
maintaining-npm.md	1224 bytes	0644
maintaining-openssl.md	5380 bytes	0644
maintaining-root-certs.md	3582 bytes	0644
maintaining-shared-library-support.md	4611 bytes	0644
maintaining-the-build-files.md	2458 bytes	0644
maintaining-types-for-nodejs.md	6190 bytes	0644
maintaining-web-assembly.md	4016 bytes	0644
maintaining-zlib.md	900 bytes	0644
node-postmortem-support.md	2588 bytes	0644
offboarding.md	943 bytes	0644
primordials.md	21339 bytes	0644
pull-requests.md	25372 bytes	0644
releases.md	41802 bytes	0644
security-model-strategy.md	2877 bytes	0644
security-release-process.md	8482 bytes	0644
security-steward-on-off-boarding.md	1040 bytes	0644
static-analysis.md	798 bytes	0644
strategic-initiatives.md	3189 bytes	0644
technical-priorities.md	6162 bytes	0644
technical-values.md	2852 bytes	0644
using-internal-errors.md	5018 bytes	0644
using-symbols.md	2376 bytes	0644
writing-and-running-benchmarks.md	23800 bytes	0644
writing-tests.md	16426 bytes	0644

File Content: commit-queue.md

File Content: `commit-queue.md`