How to Backport a Pull Request to a Release Line
Each release line has a staging branch that the releaser will use as a scratch pad while preparing a release. The branch name is formatted as follows:
N is the major release number.
For the active staging branches see the Release Schedule.
What needs to be backported?
If a cherry-pick from master does not land cleanly on a staging branch, the releaser will mark the pull request with a particular label for that release line (e.g.
backport-requested-vN.x), specifying to our tooling that this pull request should not be included. The releaser will then add a comment requesting that a backport pull request be made.
What can be backported?
The "Current" release line is much more lenient than the LTS release lines in what can be landed. Our LTS release lines (see the Release Plan) require that commits mature in the Current release for at least 2 weeks before they can be landed in an LTS staging branch. Only after "maturation" will those commits be cherry-picked or backported.
How to submit a backport pull request
For the following steps, let's assume that a backport is needed for the v10.x release line. All commands will use the
v10.x-staging branch as the target branch. In order to submit a backport pull request to another branch, simply replace that with the staging branch for the targeted release line.
- Checkout the staging branch for the targeted release line
- Make sure that the local staging branch is up to date with the remote
Create a new branch off of the staging branch
# Assuming your fork of Node.js is checked out in $NODE_DIR, # the origin remote points to your fork, and the upstream remote points # to git://github.com/nodejs/node cd $NODE_DIR # If v10.x-staging is checked out `pull` should be used instead of `fetch` git fetch upstream v10.x-staging:v10.x-staging -f # Assume we want to backport PR #10157 git checkout -b backport-10157-to-v10.x v10.x-staging # Ensure there are no test artifacts from previous builds # Note that this command deletes all files and directories # not under revision control below the ./test directory. # It is optional and should be used with caution. git clean -xfd ./test/
After creating the branch, apply the changes to the branch. The cherry-pick will likely fail due to conflicts. In that case, you will see something like this:
# Say the $SHA is 773cdc31ef $ git cherry-pick $SHA # Use your commit hash error: could not apply 773cdc3... <commit title> hint: after resolving the conflicts, mark the corrected paths hint: with 'git add <paths>' or 'git rm <paths>' hint: and commit the result with 'git commit'
- Make the required changes to remove the conflicts, add the files to the index using
git add, and then commit the changes. That can be done with
git cherry-pick --continue.
- Leave the commit message as is. If you think it should be modified, comment in the Pull Request. The
Backport-PR-URLmetadata does need to be added to the commit, but this will be done later.
- Make sure
make -j4 testpasses.
- Push the changes to your fork
- Open a pull request:
- Be sure to target the
v10.x-stagingbranch in the pull request.
- Include the backport target in the pull request title in the following format —
[v10.x backport] <commit title>. Example:
[v10.x backport] process: improve performance of nextTick
- Check the checkbox labeled "Allow edits from maintainers".
- In the description add a reference to the original PR.
- Amend the commit message and include a
Backport-PR-URL:metadata and re-push the change to your fork.
- Run a
node-test-pull-requestCI job (with
REBASE_ONTOset to the default
<pr base branch>)
- Be sure to target the
- If during the review process conflicts arise, use the following to rebase:
git pull --rebase upstream v10.x-staging
After the PR lands replace the
backport-requested-v10.x label on the original PR with