ci/backport: init #3411
Merged
ci/backport: init #3411
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds a GitHub workflow to create backport PRs when merged PRs have a "backport" label. Based on the workflow used by nixpkgs: https://github.com/NixOS/nixpkgs/blob/2566f9dc/.github/workflows/backport.yml
MattSturgeon
added
the
CI/CD
khaneliman
approved these changes
May 30, 2025
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
This pull request, with head sha This pull request will be automatically closed by GitHub.As soon as GitHub detects that the sha It is possible for this pull request to remain open if this detection does not happen, this usually happens when a force-push is done on this branch |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a GitHub workflow to create backport PRs when merged PRs have a "backport" label.
This uses the very flexible https://github.com/korthout/backport-action and is based on the workflow used by nixpkgs, which is also used by Stylix. See how it works.
Currently, the workflow will assume our backport labels follow the regex
backport ([^ ]+)$(e.g.backport nixos-25.05), however we could customise that by assigning any regex we like towith: label_pattern.Mergify also has backport support, which we've used a few times via the
@mergifyio backportcommand. While we could configure ourmergify.ymlfile to look for "backport" labels, IMO it is better to use a GitHub-based solution so that we are not locked into continuing with Mergify indefinitely.This also has the purely aesthetic1 advantage that it'll show as backported by
nixvim-ci[bot]🤩Footnotes
ok, it's not purely aesthetic. This causes github workflows to be triggered by events caused by the bot. If we used
github-actions[bot]then no workflow events would trigger. The peter-evans/create-pull-request docs explain this best. ↩