You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci: add an aggregate status check and name every job
Required status checks are matched by literal context string, and the ruleset
on dev names four of them directly: test (3.10) through test (3.13). Two
consequences. Renaming a job orphans a required check, which then waits
forever for a name nothing reports. And the list drifts: 3.14 is in the matrix
but not in the ruleset, so it has been non-blocking since it was added.
Add a single `all checks passed` job that depends on the matrix. The ruleset
can require that one context instead, leaving the matrix and the job names as
repo-side concerns.
Also name every job after what it does, which is safe to do in the same change
now that no required context points at a matrix job:
test -> run test suite on python 3.10
publish_code -> publish package and docker images
tag_commit -> tag the release commit
publish_docs -> publish the docs site
test-distros -> install and smoke-test on fedora
analyze -> scan python for security issues
benchmark -> compare performance against the base branch
cla -> check the CLA is signed
update_docs -> regenerate the docs and open a PR
update-nuclei-version -> open a PR when a new nuclei is released
update-trufflehog-version -> open a PR when a new trufflehog is released
This must merge before the ruleset is updated: a context is not selectable as
a required check until it has reported at least once. Merging this alone
changes nothing, the old required checks keep gating dev. The ruleset edit is
a separate admin step, described in the PR.
0 commit comments