PR comments

Repovex has always been a dashboard you visit. That's fine for weekly reviews, but it's the wrong place to catch a regression — by the time you check the dashboard, the change is already merged. Today we're shipping PR comments, which bring the score to where the work actually happens.

When PR comments are enabled, Repovex posts a summary comment on every pull request as soon as it's opened. The comment shows the repo's current score, how many checks are passing, and a list of any failing checks with direct links to fix them.

How it works

Turn it on with a single checkbox in settings. From then on, when a contributor opens or reopens a PR on any of your scanned repos, Repovex runs checks against the repo and adds an advisory comment. Reopening a PR updates the existing comment in place rather than spamming a new one.

Comments respect your existing configuration:

• Ignored checks don't appear in the comment or the score
• Excluded repos are skipped entirely — no comment posted
• Critical failures are listed first, with each fix link a click away

Advisory, not blocking

This is intentionally a comment, not a status check. We didn't want to land a feature that suddenly blocks merges on day one — that's a much bigger conversation, and one we'll have separately when we ship status checks. For now, PR comments give your team visibility into the score at review time without changing how PRs get merged.

Pro only

PR comments are available on the Pro plan. Upgrade to turn them on. After upgrading, you'll need to accept the updated GitHub App permissions — Repovex needs the Pull requests: Write permission to post comments, and to subscribe to the pull_request webhook event.