Skip to content
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

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

gopidesupavan
Copy link
Member

@gopidesupavan gopidesupavan commented Jan 21, 2025

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.

@potiuk potiuk merged commit dabb663 into apache:main Jan 21, 2025
92 checks passed
@potiuk
Copy link
Member

potiuk commented Jan 21, 2025

Hmmm... did not help in #45875. I had to close/reopen it to run the workflows :(

@gopidesupavan
Copy link
Member Author

gopidesupavan commented Jan 22, 2025

I think this changes also required in v2-10-test branch ?

Copy link

Backport failed to create: v2-10-test. View the failure log Run details

Status Branch Result
v2-10-test Commit Link

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
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

@potiuk
Copy link
Member

potiuk commented Jan 22, 2025

Likely :). Let's see.

dauinh pushed a commit to dauinh/airflow that referenced this pull request Jan 24, 2025
gpathak128 pushed a commit to gpathak128/airflow that referenced this pull request Jan 29, 2025
got686-yandex pushed a commit to got686-yandex/airflow that referenced this pull request Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants