potiuk opened a new pull request, #75588:
URL: https://github.com/apache/airflow/pull/75588

   A pull request gated to fork CI (AIP-120) still gets a `Tests (AMD)` run in 
apache/airflow in which the gate skips every project CI job. All of those jobs 
show up as skipped checks on the pull request, next to the fork's actual result 
in the `Fork CI / Tests (AMD)` status (seen on #75586). GitHub cannot delete or 
update individual check runs created by GitHub Actions, so the fork CI monitor 
now deletes the whole run once it has completed, which takes the skipped checks 
off the pull request.
   
   A run is deleted only when the gate, `Check if the run is needed` and `CI 
passed (project CI not run)` succeeded and every other job was skipped. Runs 
are kept when:
   
   - the tampering check counts the run as project CI work, or the pull request 
is in the `gate_bypassed` state;
   - the run's commit changes `.github/workflows/`, or its change set is too 
large to check, because such a commit could do project CI work under the gate's 
name;
   - the run is a re-run, because deleting a run deletes every attempt.
   
   The monitor needs `actions: write` instead of `actions: read`. Since the 
gated run is deleted, a maintainer who adds `use project ci` can no longer 
press **Re-run all jobs** on it. Closing and reopening the pull request starts 
project CI instead (`reopened` triggers `ci-amd.yml`). The release comment, the 
fork CI doc and the maintainer triage doc say so.
   
   Checked locally: the Breeze test suite passes (1760 passed) and the prek 
hooks pass.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5)
   
   Generated-by: Claude Code (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]

Reply via email to