Skip to content

ci: add ci-success aggregate gate#10

Merged
nickroci merged 1 commit into
mainfrom
ci/ci-success-gate
May 28, 2026
Merged

ci: add ci-success aggregate gate#10
nickroci merged 1 commit into
mainfrom
ci/ci-success-gate

Conversation

@nickroci

Copy link
Copy Markdown
Owner

Summary

  • Adds a single ci-success job that needs: [build] and passes only when the whole CI matrix (daemon / tools-search / src) is green.
  • Lets branch protection on main require just the ci-success context — adding/removing CI jobs never requires editing protection settings.
  • if: always() ensures it runs and reports red even when build fails or is cancelled (can't be skipped past a red build).

Why

main was just protected to require PRs + passing CI. This is the "one required check" that makes that low-maintenance.

Test plan

  • CI runs on this PR; ci-success turns green after the 3 matrix legs pass.
  • After merge, add ci-success as the required status check on main.

🤖 Generated with Claude Code

Add a single `ci-success` job that needs the build matrix and goes green
only if every leg (daemon / tools-search / src) passed. Branch protection
on main can then require this one context instead of enumerating each
matrix job, so adding/removing CI jobs never means editing protection.
`if: always()` makes it run and report red even when the matrix fails or
is cancelled, so it can't be skipped past a red build.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@nickroci nickroci merged commit 0d6b3f1 into main May 28, 2026
4 checks passed
@nickroci nickroci deleted the ci/ci-success-gate branch May 28, 2026 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant