adiranjan25 commented on issue #77097:
URL: https://github.com/apache/airflow/issues/77097#issuecomment-6889078899

   Hi @potiuk and Airflow maintainers,
   
   I'd like to take ownership of this issue and work on the implementation.
   
   I've reviewed the proposed approaches, and I agree that extending 
`ci-amd.yml` to handle the `pull_request.labeled` event appears to be the most 
focused solution, without introducing additional credentials or changing the 
existing fork CI monitor.
   
   My proposed approach is to:
   
   1. Add support for the `labeled` pull request event.
   2. Ensure that only the `use project ci` label triggers the project CI 
execution path, while other label events exit without starting CI work.
   3. Validate the interaction with existing fork CI gating, concurrency 
groups, and reconciliation behavior.
   4. Add focused regression tests covering the expected label-triggered 
behavior.
   5. Update the lifecycle diagram and relevant fork CI documentation.
   
   **Could you please confirm whether anyone is already working on this issue? 
If it is available, I'd be happy to take it forward and submit a PR.**
   
   I would also appreciate being assigned to the issue, if appropriate, to help 
avoid duplicate efforts.
   
   Thanks!


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

Reply via email to