Pull request review
Enable review on a repository and Hyrax reviews every pull request you open, update, or reopen — no job to submit. Each review posts a Hyrax Review check run and a comment on the PR.
Review is off until you turn it on for a repo, so you can roll it out one repo at a time.
What you get
- A comment on the pull request summarizing what Hyrax found, with each finding citing the file and lines it refers to.
- A
Hyrax Reviewcheck run on the head commit, listed next to your CI, with findings annotated on the lines they apply to. It's a red ✗ when there's a must-fix finding, neutral when the only findings are "consider"-tier suggestions, and success when the PR is clean.
A review surfaces at most 7 findings per pass — the issues that matter, not a wall of comments.
Must-fix vs consider, and gating merges
Each finding is tagged with one of two tiers:
| Tier | What it means |
|---|---|
| Must fix | A blocking-severity issue that should hold up a merge. It fails the check run (red ✗). |
| Consider | An advisory improvement worth a look, not a blocker. |
By default the check run is informational — the red ✗ appears, but Hyrax never overrides your merge policy. To make must-fix findings actually block, make Hyrax Review a required status check in your branch protection rules.
One rolling summary
Hyrax updates one summary in place as you push, rather than stacking a new comment each time. A re-review focuses on what changed, and your latest push is always what's reviewed.
Review is read-only — to turn feedback into a code change, run a fix, which opens a separate PR for you to review and merge.
Reviews are sharper on a repo that has already run Discovery — the reviewer reads your repo's published conventions instead of inferring them from the diff.
Availability
A Pro and Team workflow; not on Free. The full experience needs the Hyrax GitHub App installed, since posting comments and check runs requires write access. On a public repo added by URL (no App), you can still run a review and read the results in Hyrax — but nothing posts to GitHub, and reviews don't trigger automatically on new pull requests. See Public & private repositories.