Expand description
What a target’s own workflows say about the job --required-check names.
The trunk protection requires exactly two status-check contexts: the
named check and the title check. Every other job the project’s workflow
reports on a pull request gates nothing, and under the trunk style’s
standing arm nobody reads the check list before the merge. This reader
finds those jobs so rk setup check can name them as a limitation on
protect-trunk. It reads the workflow text line by line, in the same
spirit as the landing invariants: where a value sits somewhere this
reader does not follow, it says so rather than guessing.
Structs§
- Gate
Report - The reading and what the reader judges beside it.
- Trigger
- What a workflow’s pull-request trigger filters by.
Enums§
- Condition
- The gate job’s
ifcondition, as far as the reader proves it. - Gate
Reading - What the workflows say about the required check.
Functions§
- limitation
- The one-line limitation a report earns, or nothing where the check stands for every request-reporting job.
- read_
gate - Read every workflow under the target’s
.github/workflowsand judge the named check against the jobs that report on a pull request.