feat(ci): add CI / all-required sentinel job #23
Reference in New Issue
Block a user
Delete Branch "feat/ci-all-required-sentinel"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Renames the
.gitea/workflows/ci.ymlworkflowname:fromTest→CIand adds anall-requiredsentinel job that aggregates the Python 3.11/3.12/3.13 matrix results into a singleCI / all-required (pull_request)status context.This enables the main branch protection to use a single required-status-check entry (
CI / all-required) instead of enumerating every matrix variant (Test / test (3.11) (pull_request), etc.).Changes
.gitea/workflows/ci.yml:name: Test→name: CI.gitea/workflows/ci.yml: addedall-requiredjob thatneeds: [test], usesif: always(), and fails if any matrix variant returned non-success (failure,cancelled,skipped)What this produces
CI / test (3.11) (pull_request)CI / test (3.12) (pull_request)CI / test (3.13) (pull_request)CI / all-required (pull_request)Branch protection action required
After this PR merges, the main branch protection needs a separate BP update (out of scope for this PR):
CI / all-required (pull_request)as a required check (append, don't replace)Test / test (3.x) (pull_request)entries →CI / test (3.x) (pull_request)(or remove them onceall-requiredis sufficient)Issue: molecule-ai/molecule-sdk-python#11
Test plan
CI / all-required (pull_request)on this PR ← wait for CI🤖 Generated with Claude Code
Branch protection action (required AFTER this PR merges)
After this PR lands on
main, the main branch protection needs a separate BP update:Test / test (3.x) (pull_request)required checks →CI / test (3.x) (pull_request)CI / all-required (pull_request)as a new required checkThis is a repo settings change (requires repo admin), not a code change. Issue: molecule-ai/molecule-sdk-python#11
Pull request closed