Skip to content

ci: a push runs exactly the required set; the macOS build on dispatch in its own workflow (the owner's word of 2026-10-27, main) - #324

Merged
Calgooon merged 1 commit into
mainfrom
ci/required-set-only-main
Oct 27, 2026
Merged

Calgooon merged 1 commit into
mainfrom
ci/required-set-only-main

Conversation

@Calgooon

Copy link
Copy Markdown
Contributor

CI and docs, the stable line's copy under the pace ruling (b), on the owner's word of 2026-10-27 20:1xZ (verbatim via the keeper): "sick of seeing all these CI failures... why are none of them passing... they are all so hardcore and slowing us down". RULED fleet-wide: a push to beta or main runs exactly the required set, the same as a pull request, nothing more; the measurements run on workflow_dispatch and once before a tag, each in its own workflow with its own badge, never on the push run; the README badge points at the required-set workflow on main; a cancelled run is never a red.

What moves on main. ci.yml keeps the seven required jobs only: the build matrix is Ubuntu alone on every event; build-macos.yml holds the macOS build on dispatch (the tag's Binaries job in release.yml builds the macOS targets as before); the header comment carries the rule. README: the badges (CI on main, nightly, build-macos) and the rule in its CI paragraph; RELEASING.md step 4 names the pre-tag dispatches. actionlint clean. beta's copy, with bench.yml and differential.yml beside, is PR 323.

Refs #303.

🤖 Generated with Claude Code

@Calgooon Calgooon added ci CI, the oracle and the measurements: fixtures, floors, the ratchet, the hermetic suite, the Nightly no-changelog The PR needs no changelog.d fragment: tests only, docs only, a re-record, CI wiring (#195) labels Oct 27, 2026
…s own workflow on dispatch (the owner's word of 2026-10-27, main's copy)

The owner's word (2026-10-27 20:1xZ, verbatim via the keeper): "sick of seeing all these CI failures... why are none of them passing... they are all so hardcore and slowing us down". RULED fleet-wide: a push to beta or main runs exactly the required set (seven on main), the same as a pull request, nothing more; the measurements run on workflow_dispatch and once before a tag, each in its own workflow with its own badge, never on the push run; the README badge points at the required-set workflow on main; a cancelled run is never a red.

main's ci.yml keeps the seven required jobs only: the build matrix is Ubuntu alone on every event, the macOS build is build-macos.yml on dispatch (the tag's Binaries job in release.yml builds the macOS targets as before); the header carries the rule. README carries the badges and the rule; RELEASING.md step 4 names the pre-tag dispatches. beta's copy (bench.yml and differential.yml beside) is its own PR.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@Calgooon
Calgooon force-pushed the ci/required-set-only-main branch from 1881cf3 to 84d4a49 Compare October 27, 2026 20:22
@Calgooon
Calgooon merged commit fb683dd into main Oct 27, 2026
9 checks passed
@Calgooon
Calgooon deleted the ci/required-set-only-main branch October 27, 2026 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci CI, the oracle and the measurements: fixtures, floors, the ratchet, the hermetic suite, the Nightly no-changelog The PR needs no changelog.d fragment: tests only, docs only, a re-record, CI wiring (#195)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant