Repository navigation
Update korthout/backport-action action to v4.7.2 - #248
Closed
renovate[bot] wants to merge 1 commit into
Closed
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
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
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.
This PR contains the following updates:
v4.7.1→v4.7.2Release Notes
korthout/backport-action
v4.7.2: Backport-action v4.7.2Compare Source
What's Changed
Thanks to two contributions by @bahimehdi, this release fixes two bugs. Neither needs any configuration.
With
comment_style: legacy, the action posts an explanatory comment when the original pull request isn't merged, or when it contains merge commits withmerge_commits: fail. Previously, if GitHub rejected that comment, the job could crash. Now the action logs the failure and doesn't fail the job, as it already did for the summary comment.With
merge_commits: skip, a pull request that contains only merge commits was reported as a failed backport for every target branch, with instructions to cherry-pick no commits. Withexperimental.conflict_resolution: draft_commit_conflicts, the action instead pushed an unchanged backport branch for each target branch. Now the action explains once, on the original pull request, that there is nothing to backport and why, and doesn't touch any target branch. It setswas_successfultotrue, as it does when every target branch already contains the changes. Withcomment_style: summary, that looks like this:The summary comment also no longer says "backported this pull request" when every target branch was skipped, for example because its backport pull request already exists. It now says "found nothing left to backport from this pull request".
The README now explains how to run CI on your backport pull requests right away. With the default
GITHUB_TOKEN, CI doesn't run on backport pull requests, or its runs wait for approval. The new Run CI on backport pull requests section shows how to give the action a GitHub App token instead, and pass it to bothactions/checkoutand the action. The README also explains what public repositories need to do before GitHub blockspull_request_targeton December 2, 2026: allow the event for the backport workflow in an Actions policy (andissue_commenttoo, if you trigger backports with a comment).New Contributors
Maintenance changes
Full Changelog: korthout/backport-action@v4.7.1...v4.7.2
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.