chore(ci): remove unused reviewer integrations from the review floor

Draft
YA
18d ago
+1-1

User description

What

Removes unused reviewer integrations from the review-liveness floor in .github/workflows/auto-merge.yml.

The floor counts DISTINCT external review publishers that finished non-failing on the PR head, matched by the LLM_RE pattern. Two names in that pattern belong to reviewer integrations that no longer report on this repository, and one belongs to a hosted service that is not used here (the self-hosted pr-agent lane runs as a github-actions job, which the floor already excludes by design, so it is unaffected). This PR drops those three names from LLM_RE. cubic stays in the pattern. Nothing else in the workflow changes.

Why this is safe: the floor stays satisfiable

The floor defaults to MIN_REVIEWERS=2 distinct publishers. I checked the check-runs and commit statuses on recent PR heads in this repository. The reviewers that still report there, and that still match the pattern after this change, are:

  • cursor check-runs (success/neutral both count)
  • macroscopeapp check-runs (Approvability Check, neutral)
  • sourcery-ai check-runs (success on most PRs)
  • CodeRabbit and Devin commit statuses (these carry no creator login, so together they count as one publisher)

That leaves at least two distinct publishers on a typical PR, so the floor can still be met. The floor itself, the threshold and the defer/refuse logic are untouched. Removing names from the pattern can only make the floor stricter, never looser.

Verification

  • actionlint on the changed workflow file(s): clean (exit 0)
  • Repo lint and tests: npm run lint (redocly): valid, with 58 pre-existing warnings; npm run test:ga 35 passed / 0 failed. The change is workflow-only, so these are regression receipts rather than coverage of the change.
  • Self-reviewed diff: a one-line regex change only

Not in scope

  • Historical comments in scripts and tests that credit past review feedback are left alone, because they record what happened and are not wrong about current behaviour.
  • The self-hosted pr-agent workflow is intentionally kept.

Draft. Do not merge until a maintainer has reviewed it.

🤖 Generated with Claude Code

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Summary by Sourcery

Enhancements:

  • Update the auto-merge review-liveness floor to recognize only active reviewer integrations.

CodeAnt-AI Description

Remove retired reviewer integrations from the auto-merge review floor

What Changed

  • The auto-merge review-liveness check no longer counts retired reviewer integrations or unused vendors.
  • The existing reviewer threshold and defer behavior remain unchanged, so only currently reporting external reviewers can satisfy the floor.

Impact

✅ Prevents inactive reviewers from satisfying merge requirements
✅ Keeps auto-merge checks aligned with active review providers

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.