backport: Modernise the backport workflow#82
Merged
Conversation
The workflow used the deprecated zeebe-io/backport-action@v0.0.4 and relied on the default GITHUB_TOKEN, which is read-only by default, so it could not actually create the backport branches and pull requests. Switch to the maintained korthout/backport-action@v4, grant the required contents and pull-requests write permissions, and bump actions/checkout to v4. Trigger on both 'closed' and 'labeled' so a 'backport <branch>' label backports automatically on merge whether it was added before or after merging, with no manual /backport comment. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
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
1 participant
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.
The backport workflow used the deprecated
zeebe-io/backport-action@v0.0.4and relied on the defaultGITHUB_TOKEN, which is read-only by default, so it could not actually create the backport branches and pull requests.This switches to the maintained
korthout/backport-action@v4, grants the requiredcontentsandpull-requestswrite permissions, and bumpsactions/checkoutto v4. It triggers on bothclosedandlabeled, so abackport <branch>label backports automatically on merge whether the label was added before or after merging, with no manual/backportcomment.Pairs with the
backport wrynose/backport scarthgaplabels.