-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ready_for_review to workflow pull_request types #45855
Add ready_for_review to workflow pull_request types #45855
Conversation
Hmmm... did not help in #45875. I had to close/reopen it to run the workflows :( |
I think this changes also required in v2-10-test branch ? |
Backport failed to create: v2-10-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker dabb663 v2-10-test This should apply the commit to the v2-10-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
Likely :). Let's see. |
We have added draft config option for backport automation, which creates pr in draft state. When we sets to ready for review the workflow needs to be triggered but it requires ready_for_review type.
We have see this today in #45826 , workflow not triggered, due to ready_for_review type missing.
^ 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.rst
or{issue_number}.significant.rst
, in newsfragments.