Repository navigation
ci: share the cron gate and verdict head through one reusable workflow (#1967) - #2002
Conversation
|
GOOD TO GO at
I ran the files the review did not, all passing: Unverified: what |
949779d to
4b2bc49
Compare
- Conda Update, Vendor Update and GitHub Pages each carried the same test gate and `verdict` job. Both now live in cron-head.yml, a `workflow_call` workflow that each calls as its `head` job; the acting jobs read `needs.head.result` and `needs.head.outputs.verified`. - The Saturday schedules are spread eight hours apart (Pages 02:00, Vendor 10:00, Conda 18:00 UTC), so no two heads gate the same commit at once and Conda Update follows Vendor Update's release. - Triggers otherwise, concurrency groups, environments, deploy-key steps and permissions are unchanged; the head holds `contents: read` only. - Tests: the verdict and conda gate tables decide the head's jobs against cron-head.yml; new tests pin that the three call one head and the spread. - Docs: workflows.rst gains the Cron Head row, node, calls and schedule rationale, cited by name; pep.rst drops a line citation.
4b2bc49 to
fc192dd
Compare
|
GOOD TO GO at A Sonnet delta review confirmed:
|
|
Coverage: 91.54% (unit tier, Python 3.15,
Per-file detail: the |
make pylint,make mypy,make isort)make testpasses, and a test case covers the changeWhat is the purpose of your pull request?
ci— workflows or build toolingDescription of your pull request and other information
Step 6 of #1967. Conda Update, Vendor Update and GitHub Pages each carried the same gate (
unit-testswithgate-onlyunless the event is a pull request or aworkflow_run) and the sameverdicthead. That head now lives once, in the new reusablecron-head.yml, which isworkflow_callonly and grantscontents: read.Each of the three replaces those two jobs with a
headjob ("Conda gate", "Vendor gate", "Docs gate"). Their acting jobs now readneeds.head.resultandneeds.head.outputs.verified.The following are unchanged:
repository-maintenance;environment:lines, deploy-key steps and per-job permissions;!cancelled()on every acting job;vendor-updatejob name, which Create Release reads.Not done: a single weekly gate. It would move publish times, because Pages runs at 02:00 and Vendor and Conda at 10:00. Each would also publish main's tip at gate time rather than at its own schedule. That needs a ruling, which I'll ask for on #1967.
Checks:
contents: read. Against the old layout, 13 of them fail.tests/projectfiles pass.Part of #1967.