Skip to content

ci: add a ci-gate job as the single required status check - #10

Closed
mark-brannan wants to merge 3 commits into
mainfrom
claude/ci-gate
Closed

ci: add a ci-gate job as the single required status check#10
mark-brannan wants to merge 3 commits into
mainfrom
claude/ci-gate

Conversation

@mark-brannan

Copy link
Copy Markdown
Owner

Adds one ci-gate job that fans in this workflow's PR jobs, so the branch ruleset can require a single context.

Requiring the matrix legs directly is brittle: rename or drop one and the ruleset silently enforces something different, or waits forever on a context that never reports. always() is there so a skipped dependency fails the gate rather than skipping it.

Groundwork for branch protection plus Mergify auto-update across the repos — mirrors signalk-noaa-space-weather.

🤖 Generated with Claude Code

The branch ruleset needs one context to require. Requiring the matrix legs
directly means a renamed or dropped leg silently changes what is enforced,
and a required context that never reports blocks every pull request.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Sep 3, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 203612ea-6d1b-42b5-a959-829b4cb84927


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

CodeQL flags a job that does not limit GITHUB_TOKEN. This one reads nothing
and writes nothing -- its verdict comes from `needs` -- so the right scope is
no permissions at all.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The comment conflated two different skips. A job skipped by `if` reports
`skipped`; a workflow skipped by path or branch filters leaves its check
pending. Neither is the explicit verdict a ruleset needs, which is the
reason for `always()` -- not the "never reports" story the comment told.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@mark-brannan

Copy link
Copy Markdown
Owner Author

Folded into #9, which now carries the ci-gate job, the Mergify config and the fingerprint-gated Claude review as one change. Closing this so the repo gets one review instead of two, and so there is no merge order to get wrong.

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