Skip to content

ci: make Ready gate fail when required jobs fail - #780

Open
omercnet wants to merge 2 commits into
mainfrom
ci/ready-gate-fail-on-failure
Open

ci: make Ready gate fail when required jobs fail#780
omercnet wants to merge 2 commits into
mainfrom
ci/ready-gate-fail-on-failure

Conversation

@omercnet

@omercnet omercnet commented Aug 1, 2026

Copy link
Copy Markdown
Member

The 🚀 Ready gate (the only required status check on main) has no if: always(), so when any upstream job fails the gate is skipped
and GitHub treats a skipped required check as satisfied. Combined with auto-approve + auto-squash, PRs merge over red CI (e.g. #776). This makes the gate
run always and fail explicitly if any required job failed or was cancelled.

  Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@shuni-bot

shuni-bot Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

🐕 Review complete — View session on Shuni Portal 🐾

@shuni-bot shuni-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🐕 Shuni's Review

Makes the 🚀 Ready gate run with if: always() and fail explicitly when any needs job reports failure/cancelled, so a skipped gate can no longer auto-satisfy branch protection.

Logic checks out: needs.*.result is valid in a step-level if, contains() does exact element matching, and treating skipped as a pass is correct here since pr-title-check is intentionally skipped on push to main. build/eslint/gitleaks/unit-test have no if: and no needs, so they can't be silently skipped. ci.yml is the only workflow with this gate pattern — nothing else to update.

No blocking issues — good bones! One 💡 NIT inline. Woof!

Comment thread .github/workflows/ci.yml Outdated
Co-authored-by: shuni-bot[bot] <251468265+shuni-bot[bot]@users.noreply.github.com>
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