Skip to content

feat(ci-gate): add the profile for hyperpolymath/tsunami-breaker - #156

Merged
hyperpolymath merged 2 commits into
mainfrom
add/ci-gate-profile-tsunami-breaker
Nov 19, 2026
Merged

hyperpolymath merged 2 commits into
mainfrom
add/ci-gate-profile-tsunami-breaker

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Why

The Branch-Floor ruleset requires the status CI/gate on hyperpolymath/tsunami-breaker. That repo has no ci-gate.yml caller and no profile here, and the gate fails closed without a profile. So no pull request there can merge (tsunami-breaker#13 was refused with Required status check "CI/gate" is expected).

This PR is step 1 of 2. Step 2 is the caller in tsunami-breaker, pinned to the merge commit of this PR.

What

  • profiles/ci-gate/hyperpolymath/tsunami-breaker.json: 13 required checks from 11 workflows.
  • profiles/ci-gate/README.adoc: the commits read and the reason for one exclusion.

How the list was derived

By the rule in profiles/ci-gate/README.adoc. A workflow is listed only if its run passed on the pull request head 705dfee (PR 13) and on the latest main, 957ea0e. It has no path filter and no continue-on-error on the job.

One difference from the earlier rows, stated in the README: the read was of workflow runs and their conclusions through the authenticated API on 2026-11-19. The job display names were taken from the workflow files at the pull request head, not from check runs.

Not listed: mint-gates (quality.yml). That workflow ended as startup_failure on the pull request head, because it calls an action that the organisation policy refuses. The template is fixed (rsr-template-repo#456), and tsunami-breaker did not take that fix yet. When it does, mint-gates can be added.

Checked

  • scripts/validate-ci-gate-profile.sh profiles/ci-gate/hyperpolymath/tsunami-breaker.json hyperpolymath/tsunami-breaker: exit 0.
  • tests/ci-gate.sh: 549 passed, 0 failed.

Not run: the other test scripts in tests/.


Generated by Claude Code

The Branch-Floor ruleset requires CI/gate on tsunami-breaker, and the
gate fails closed for a repository with no profile, so no pull request
there can merge.

The list follows the rule in profiles/ci-gate/README.adoc: a workflow is
listed only if it passed on the pull request head (705dfee, PR 13) and on
the latest main (957ea0e). mint-gates (quality.yml) is left out: it ended
as startup_failure on the pull request head.

Checked: scripts/validate-ci-gate-profile.sh exit 0; tests/ci-gate.sh
549 passed, 0 failed.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZntqhzSQniUqkmByZb
@coderabbitai

coderabbitai Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Documentation
    • Added CI evidence for pull requests and commits to the main branch, including the reason a workflow was excluded.
  • New Features
    • Added gate configuration listing the required checks for the repository.

The change adds a schema-version 2 CI gate profile for hyperpolymath/tsunami-breaker and updates the README with repository evidence and check details.

Changes: tsunami-breaker CI gate profile

Layer / File(s) Summary
Profile and repository evidence
profiles/ci-gate/hyperpolymath/tsunami-breaker.json, profiles/ci-gate/README.adoc
The profile lists 13 required check/workflow pairs, including two Empty-linter entries. The README records the pull-request and main commits, lists the Rust and rust-secrets checks, and explains that mint-gates is excluded because its workflow ended in startup_failure on the pull-request head.

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Other

Possibly related PRs

Merge Risk: Minimal · up to 7741f

This adds a CI gate profile for tsunami-breaker and documents how its required checks were chosen. No concrete defect was found, and the change is easy to revert. The only residual uncertainty is that per-job results on the recorded commits were not checked, which the author or reviewers can confirm in the Actions UI before step 2 pins this commit.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the change: adding a ci-gate profile for hyperpolymath/tsunami-breaker. The changeset adds that profile JSON and updates the ci-gate README. The title is short and specific. It uses th…
Description check Passed The description explains why the profile is needed, how the 13 required checks were derived, which workflow was excluded and why, and which validation steps were run. It matches the changeset closely.
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title names the change: adding a ci-gate profile for hyperpolymath/tsunami-breaker. The changeset adds that profile JSON and updates the ci-gate README. The title is short and specific. It uses the conventional commit prefix, which does not reduce clarity.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 180d2dbc-4108-444a-8b3b-a930c9a8df81
Commits

Reviewing files that changed from the base of the PR and between 20078aa and 7741fa5.

Files selected for processing: 2

  • profiles/ci-gate/README.adoc
  • profiles/ci-gate/hyperpolymath/tsunami-breaker.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Recent review details

Context from checks skipped due to timeout: 2

  • GitHub Check: CodeRabbit
  • GitHub Check: gate-pr / CI gate
Additional comments: 1

profiles/ci-gate/hyperpolymath/tsunami-breaker.json: 1

1-1: Stability & Availability

The reported claim depends on whether scan / rust-secrets reported as a successful job on both commits in hyperpolymath/tsunami-breaker. The inspected repository source does not show a skip condition for that job. The tsunami-breaker caller and run data could not be inspected, so the claim cannot be decided. No correction is supported.

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 19, 2026 03:12
@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath merged commit 51504ef into main Nov 19, 2026
26 checks passed
@hyperpolymath
hyperpolymath deleted the add/ci-gate-profile-tsunami-breaker branch November 19, 2026 03:28
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.

3 participants