Yes Great question :), When the backport succeeds or failed, a comment will be added to original PR
eg: https://github.com/apache/airflow/pull/44081#issuecomment-2480855391 Regards, Pavan Kumar On Mon, Nov 18, 2024 at 12:42 PM Tzu-ping Chung <t...@astronomer.io.invalid> wrote: > > What happens if a back port cannot be created automatically? (Or asked > another way, how do I know when I need to manually do the back port PR?) > > > > On 18 Nov 2024, at 20:35, Pavankumar Gopidesu <gopid...@apache.org> wrote: > > > > Hello All, > > > > We have set up Cherry Picker Automation that supports both automated > > and manual backporting to any branch. > > > > 1. For automated backporting, simply add the required labels to your > > PR (eg, backport-to-v2-10-test, backport-to-v2-9-test) > > > > 2. Once the PR is merged, the changes will be automatically backported > > if there are no conflicts. > > > > If needed, manual backporting is still an option as well. > > > > Please find the detailed documentation here. > > > > https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-github-actions. > > > > Thanks to @uranusjr and @amoghrajesh for the initial suggestions. > > > > Thanks to Jarek, Advocating at Cherry-picker repository. > > > > Regards, > > Pavan Kumar > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > > For additional commands, e-mail: dev-h...@airflow.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
