potiuk opened a new pull request, #76154: URL: https://github.com/apache/airflow/pull/76154
Follow-up to #76148. The fork CI monitor's per-job commit statuses are its largest use of the `GITHUB_TOKEN` limits that every workflow of `apache/airflow` shares (500 content-creating requests an hour, 80 a minute). During the pilot they already fill the monitor's per-run budget whenever a couple of full-matrix fork runs are active. This makes room before fork CI is enabled for every contributor. - **Only finished jobs get a status.** Queued and running jobs no longer get a `pending` status, so each job costs one write instead of two (about 127 fewer writes for a full-matrix run). `Fork CI / Tests (AMD)` already shows the run as running and links it, and with the monitor's 15-minute cadence a per-job "running" status lagged behind the fork's own run page anyway. - **Smaller per-run budget:** 60 → 40 writes per run, of which `CI run started` takes at most 20. Job statuses are capped at 160 writes an hour (32% of the content-creating limit), and each run stays well under the 80-a-minute limit. - **The limits are now observable.** Each run logs the token's remaining REST and GraphQL quota (`GET /rate_limit`, which does not count against it) and how many calls GitHub rate-limited. Rate limiting in two runs in a row adds a note to the monitor's Slack message, tracked in the same record as the deferred-job-status count. `dev/AGENTS.md` lists the new signals. Tests: `uv run --locked pytest` in `dev/breeze` (2292 passed), `prek run mypy-dev`, and the pre-commit and manual prek stages pass. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (please specify the tool below) Generated-by: 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]
