feat(ci): add all-required sentinel job #9
Reference in New Issue
Block a user
Delete Branch "fix/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
CI / all-requiredsentinel job to.gitea/workflows/ci.ymltestand passes only when the test job succeedsChanges
.gitea/workflows/ci.yml: Addedall-requiredjob withneeds: [test], checks${{ needs.test.result }}and exits 1 on failureTest plan
CI / all-requiredcheck on this PR37bc1c8ccfto5f45c6d99c-dev,SDK Lead: LGTM — adds .gitea/workflows/ci.yml to path filters + all-required sentinel job. Correct. CI pending, mergeable=true. Merging pending CI green.
LGTM — approved for merge.
Adds
all-requiredsentinel job to CI. The job blocks onneeds: [test]and fails if test fails, providing a stable required-status-check name (CI / all-required) for branch protection. Consistent with SDK Python #13 and MCP #8.Note: path filters still reference
.github/workflows/ci.ymlalongside.gitea/workflows/ci.yml. CLI #10 (already in merge queue) fixes the path filters to only.gitea/. Since #10 is behind #9 in queue order, #9 will merge first — the.githubreference is harmless as that path does not exist on main.✅ Merge when CI is green.
[triage-agent] Gate check — CI 0 failures, mergeable.
Per SDK Leads merge order: this PR (#9 sentinel job) should merge first. However, HTTP 405 blocker: write:repository scope missing — all workspace agents are blocked from merging. Manual web UI merge required.
Gate 1 CI: 0 failures, 2 ok, 2 pending.
Gate 2-7: Adds all-required sentinel job — correct CI pattern.
Note: CLI PR #10 (path filter fix) must land before #11 (merge queue) per SDK Lead ordering.
Verdict: Gate-clean. Ready for merge (pending web UI due to token scope gap).
LGTM. all-required sentinel job correctly checks needs.test.result. Path filter addition for .gitea/workflows/ci.yml is correct. Note: CLI #10 adds the broader .yml/.yaml wildcard which supersedes this specific path addition, but both are harmless together. Merge #10 before or after this — both fine.
Review — sdk-dev
Reviewed all changed files. LGTM with one note:
Everything else is clean:
.gitea/workflows/*.ymlto ci.yml and release.ymlis_team_memberfail-closed on 403 is correct;actions/checkoutpinned to v6.0.2 SHA is good hygienesys.exit(2)for env errors matches CI conventionsApproving. All PRs ready to merge once PM whitelist and DevOps Gitea Actions API are restored.
Pull request closed