Repository navigation
automation: trigger the edera/6.18-lts backport when a PR merges - #22
Merged
Merged
Conversation
edera/6.18-lts proposes a backport of each pull request merged into edera/mainline, driven by its own workflows. Add a workflow here whose only job is to dispatch that, skipping pull requests labelled no-backport and the nightly's rebase pull requests.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
lts-backport-trigger.yml. Its only job: when a PR merges intoedera/mainline, it runsgh workflow run kernel-nightly.yml --ref edera/6.18-lts -f backport_pr=<N>, which starts that tree's own backport workflow. Nothing else on mainline changes.no-backport, and the nightly'srebase/...PRs.edera/6.18-lts, including whether there is anything to backport. Automation-only PRs come out as nothing to do there.pull_request_target, so it runs this branch's copy of the file with a token that can start runs even for PRs from forks. It never checks out PR code.Merge #21 first. Until then, the dispatch fails because
backport_prdoesn't exist on 6.18-lts yet.