Skip to content

ci: Gatehouse review advisory by default (v0.4.0)#564

Merged
fatherlinux merged 1 commit into
masterfrom
chore/gatehouse-advisory-v0.4.0
Jul 6, 2026
Merged

ci: Gatehouse review advisory by default (v0.4.0)#564
fatherlinux merged 1 commit into
masterfrom
chore/gatehouse-advisory-v0.4.0

Conversation

@fatherlinux

Copy link
Copy Markdown
Member

Bumps the Gatehouse reusable review workflow to @v0.4.0, which is advisory by construction — it exits 0 regardless of findings and posts a plain COMMENT review instead of REQUEST_CHANGES.

Why

This repo's Gatehouse review check was marked a required status check, which let a non-deterministic LLM finding block merges (see crunchtools/gatehouse#23). The required-check has already been removed from branch protection; this PR aligns the workflow file:

  • Pins review.yml@v0.2.0@v0.4.0 (advisory default).
  • Corrects the guidance that told adopters to mark the review job required — only the Protect workflows guard is a blocking gate (per crunchtools constitution §XII).

No secrets or job structure change.

🤖 Generated with Claude Code

Bumps the reusable review workflow to v0.4.0, which is advisory by
construction (exits 0, posts a COMMENT). The review job is no longer a
required status check — per crunchtools constitution XII, only the
`Protect workflows` guard blocks merges.

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

Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@fatherlinux fatherlinux merged commit 7a76a65 into master Jul 6, 2026
4 of 5 checks passed
@fatherlinux fatherlinux deleted the chore/gatehouse-advisory-v0.4.0 branch July 6, 2026 15:09
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