github-actions[bot] commented on PR #76136: URL: https://github.com/apache/airflow/pull/76136#issuecomment-6544746842
<!-- workflow-approval: ci-change --> **Your CI change needs a maintainer.** CI for this pull request runs in your fork, and the workflow runs it starts in apache/airflow are approved automatically while they only run the fork CI gate. This pull request changes files that define what CI runs: - `dev/breeze/doc/08_ci_tasks.rst` - `dev/breeze/doc/ci/08_fork_ci_for_external_contributors.md` - `dev/breeze/src/airflow_breeze/utils/ci_audit.py` - `dev/breeze/tests/test_ci_audit.py` Such a change can make project CI run on the project's runners, so its workflow runs in apache/airflow wait for a maintainer to review the change and approve them. CI in your fork is not affected, and its result stays visible on this pull request. Pull requests from contributors run their CI in the contributor's own fork. GitHub Actions is free and has no minute limit on public forks, while the CI capacity of the Apache Software Foundation is shared by every ASF project and is finite. --- _This comment was posted automatically by the fork CI monitor from templates drafted with an AI-assisted tool, so it may contain mistakes. An Apache Airflow maintainer, a real person, will review the pull request once its fork CI is green. [Why the first pass is automated](https://github.com/apache/airflow/blob/main/contributing-docs/25_maintainer_pr_triage.md#why-the-first-pass-is-automated)._ -- 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]
