Add copy-pasteable cherry-picker command if it fails to cherry-pick #44316
Conversation
This file contains 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
When cherry-picker fails to backport a PR it adds a message to the PR explaining the failure and linking to the commit. This PR also adds a copy&pasteable cherry-picker command that the maintainer should run to retry it locally. It also explains what maintainer should do after solving the conflicts.
potiuk
requested review from
uranusjr,
ephraimbuddy,
gopidesupavan,
eladkal,
utkarsharma2 and
kaxil
kaxil
approved these changes
Nov 24, 2024
kaxil
added
the
changelog:skip
|
Yeah, good one :) |
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.
When cherry-picker fails to backport a PR it adds a message to the PR explaining the failure and linking to the commit. This PR also adds a copy&pasteable cherry-picker command that the maintainer should run to retry it locally. It also explains what maintainer should do after solving the conflicts.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.