potiuk opened a new pull request, #75814: URL: https://github.com/apache/airflow/pull/75814
The fork CI monitor read a contributor's `Tests (AMD)` workflow state only until it first saw the workflow enabled. When the workflow was disabled after that, the pull request stayed in `awaiting_push` forever. Its comment kept saying "The workflow is enabled in your fork", and the `Fork CI / Tests (AMD)` status never resolved. #75695 got stuck this way. - **Reconciler:** reads the workflow state on every run for any pull request with no fork run for its head commit, `awaiting_push` included. `disabled_inactivity` (GitHub disabling the workflow after 60 days without activity in the fork) now counts as setup required instead of being reported as an unexpected state. - **New comment:** when fork CI that had worked stops because the workflow is disabled or missing, the monitor posts a new comment, so the author is notified (an edit to the state comment would not notify them). The comment says why it stopped and how to turn it back on. - **Setup instructions:** every setup text now starts with syncing the fork's `main` from apache/airflow (`gh repo sync <fork> --branch main`), then enabling the workflow, then pushing. - **`breeze ci audit`:** no longer suggests that committers, collaborators or exempted contributors disable the workflow. A committer trying fork CI with `use fork ci` needs it enabled, and following that hint is one way a pull request ends up stuck like this. The new comment has the same gap as the existing "push again" comment: if posting it fails after the state comment was updated, it is not retried. That is tracked in #74908, which should cover both. related: #75695 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Claude Opus 5) Generated-by: Claude Code (Claude Opus 5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
