potiuk opened a new pull request, #76835:
URL: https://github.com/apache/airflow/pull/76835
## Why
When a contributor's fork blocks the `Tests (AMD)` workflow (Actions
settings that do not allow
all actions, or an invalid workflow file), the fork run ends in "Startup
failure" with no jobs.
The fork CI monitor reported it like any failed run, asking the author to
"fix the failures", so
the pull request did not say what went wrong or where to look (seen on
#76536 during the
AIP-120 vote). The bot's "How this works" link also pointed to the design
document instead of
the contributor documentation, as suggested in the vote thread.
## What
- A fork run that ends in `startup_failure` keeps the `failed` handling, but
`Fork CI / Tests (AMD)` says "Fork CI run could not start - check your
fork's Actions settings"
and the state comment explains that no job ran, what to check in the
fork's Actions settings,
and that the run page shows GitHub's error.
- Links in fork CI comments point to the "CI in your fork" section of
`contributing-docs/18_contribution_workflow.rst`, which now covers startup
failures; that
section links the design document for maintainers.
Not covered: when Actions is disabled for the whole fork no run exists at
all, and the monitor
cannot tell that apart from a branch that was not pushed yet.
related: https://lists.apache.org/thread/5603zwgpj7pgj6j979hbgpr72xsjbbws
---
##### 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]
