bugraoz93 commented on PR #70241: URL: https://github.com/apache/airflow/pull/70241#issuecomment-5062198787
> > > ### Backport failed to create: airflow-ctl/v0-1-test. View the failure log [ Run details ](https://github.com/apache/airflow/actions/runs/30029777960) > > > Note: As of [Merging PRs targeted for Airflow 3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x) the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches. > > > > > > In matter of doubt please ask in [#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) Slack channel. > > > > > > Status Branch Result > > > ❌ airflow-ctl/v0-1-test [](https://github.com/apache/airflow/commit/94b9fe33284b3067205d753916af118d18daf0c2) > > > You can attempt to backport this manually by running: > > > > > > ```shell > > > cherry_picker 94b9fe3 airflow-ctl/v0-1-test > > > ``` > > > > > > This should apply the commit to the airflow-ctl/v0-1-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: > > > > > > ```shell > > > cherry_picker --continue > > > ``` > > > > > > If you don't have cherry-picker installed, see the [installation guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli). > > > > Anything I should do @bugraoz93 ? > > We don't need backport of generated models, let me remove the label too so we won't check while releasing if check needed. Thanks for checking Vincent! We need to create according to state of support during release while fast forwarding -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
