Repository navigation
Update korthout/backport-action action to v4.7.1 - #228
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
This branch has not been deployed
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.0→v4.7.1Release Notes
korthout/backport-action
v4.7.1: Backport-action v4.7.1Compare Source
What's Changed
Thanks to a contribution by @jrasm91, backports no longer fail when you combine
auto_merge_enabled: truewithexperimental.conflict_resolution: draft_commit_conflicts. Previously, when a cherry-pick conflicted, the action created the draft backport pull request and then tried to enable auto-merge on it. GitHub doesn't allow auto-merging of drafts, so the backport was reported as an unexpected failure,was_successfulwas false, and the draft backport pull request didn't receive instructions on how to resolve the conflict.Now the action doesn't attempt auto-merge on a draft backport pull request and logs it. The backport is reported as drafted with conflicts, and the draft receives the conflict-resolution instructions as usual. With
comment_style: summary, that looks like this:Auto-merge stays off for the draft. You can enable it once you've resolved the conflicts.
New Contributors
Updated dependencies
Maintenance changes
Full Changelog: korthout/backport-action@v4.7.0...v4.7.1
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.