Repository navigation
ci: converge matrix to single 'CI' required-check job - #44
Merged
Merged
Conversation
Compute the next version from today's date and the most recent calver tag, then pass it via release-as so every push to main produces a release PR (e.g. 2026.9.1, 2026.9.2, 2026.10.1). Same-month pushes bump the patch counter; new months reset to patch 1. release-please has no native calver strategy, so this overrides its conventional-commit-derived version with the computed one each run.
PRs to main show nine separate status checks (Python matrix × 6 platforms + Mojo + CodeQL + Socket Security), which makes branch ruleset configuration brittle — each platform combination would need to be listed. Add a final ``ci`` job that waits on the Python matrix and treats the Mojo job as informational (Mojo toolchain is nightly-quality, not a blocker). The ``ci`` job is the single required status check on the main branch ruleset. Reviewers see one green tick; the underlying matrix detail is still visible on the PR. - Adds ``needs: [python, mojo]`` + ``if: always()`` convergence job - Python matrix failure → ``ci`` fails - Mojo failure → ``ci`` stays green, surfaces as ``::warning::``
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a convergence job that waits on the Python matrix and treats the Mojo job as informational. The new `ci` job is the single required status check on a new main-branch ruleset (follow-up commit).
Before: 9 separate checks on every PR → 9 individual checks required in branch protection / rulesets.
After: 1 `ci` check that fans out internally → ruleset requires just `ci`.
Why
Changes
```.github/workflows/ci.yml`
Follow-up
A second commit (or a follow-up PR) creates the main-branch ruleset requiring `ci`. The ruleset can't apply retroactively to a merged PR — it'll govern future merges from this point on.
Testing
This PR itself is the test. CI will show 1 green `CI` check + the 9 underlying checks; the merge button enables off the single check.