Home Explore Blog CI



nix

maintainers/backporting.md
d94b85dcd5da01f15ef3a4e77141ad73a7dbb26b299c121e000000030000035a

# Backporting

To [automatically backport a pull request](https://github.com/NixOS/nix/blob/master/.github/workflows/backport.yml) to a release branch once it's merged, assign it a label of the form [`backport <branch>`](https://github.com/NixOS/nix/labels?q=backport).

Since [GitHub Actions workflows will not trigger other workflows](https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#triggering-a-workflow-from-a-workflow), checks on the automatic backport need to be triggered by another actor.
This is achieved by closing and reopening the backport pull request.

This specifically affects the [`installer_test`] check.
Note that it only runs after the other tests, so it may take a while to appear.


Chunks
82bf049f (1st chunk of `maintainers/backporting.md`)
Title: Backporting Pull Requests
Summary
To automatically backport a merged pull request to a release branch, assign it a label in the format `backport <branch>`. Because GitHub Actions workflows don't trigger other workflows, backport pull requests need to be closed and reopened to trigger checks like `installer_test`.