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
The checks list on a PR was a wall of internal job ids. 'test (3.10)' says a
job ran, not what it checked; 'publish_code' and 'tag_commit' are identifiers
that were never meant to be read by a human deciding whether a PR is safe to
merge.
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
Names only, no behavior change.
Note this renames the status check contexts. The branch ruleset on dev still
requires the old names, so it needs updating in the same window or required
checks will sit pending forever.
0 commit comments