Re: [PR] Switch to using envvar rather htan flag for --include-commits [airflow]

2025-05-17 Thread via GitHub


github-actions[bot] commented on PR #50709:
URL: https://github.com/apache/airflow/pull/50709#issuecomment-2888347692

   ### Backport failed to create: v3-0-test. View the failure log  Run details 

   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-0-test
   https://github.com/apache/airflow/commit/6e17e73168677a3df092631d764b2f5a92ccf95c";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 6e17e73 v3-0-test
   ```
   
   This should apply the commit to the v3-0-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:
   
   ```bash
   cherry_picker --continue
   ```
   


-- 
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]



Re: [PR] Switch to using envvar rather htan flag for --include-commits [airflow]

2025-05-17 Thread via GitHub


potiuk merged PR #50709:
URL: https://github.com/apache/airflow/pull/50709


-- 
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]



Re: [PR] Switch to using envvar rather htan flag for --include-commits [airflow]

2025-05-16 Thread via GitHub


potiuk commented on PR #50709:
URL: https://github.com/apache/airflow/pull/50709#issuecomment-2887524981

   Another one needed when we build old tags :)


-- 
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]