Integrations
Hyrax connects to the tools your team already uses. GitHub is the core integration — it's how Hyrax reads your code and ships its work. Ticketing through Linear is opt-in.
| Integration | Status | What it does |
|---|---|---|
| GitHub | Generally available | Reads your code, opens pull requests, posts PR review comments and check runs. |
| Linear | Generally available | Files a ticket when you fix an observation on a configured repo. |
GitHub
After you sign in, connect your GitHub organization by installing the Hyrax GitHub App on the repositories you want analyzed. There are no personal access tokens to manage and nothing to paste — once the App is installed, Hyrax reads your code and runs jobs securely. See Security for how access works.
On every plan, public repositories can also be connected in anonymous mode — read-only, no App required. See Public & private repositories.
What Hyrax writes back
Everything Hyrax opens on your repo is clearly attributed:
| Surface | Behavior |
|---|---|
| Pull requests | Titled with a [Hyrax] prefix. Fixes open a PR on a dedicated hyrax/ branch; you review and merge it like any other PR. |
| PR reviews | A single review comment summarizing the findings (each tagged must-fix or consider), plus a Hyrax Review check run on the PR head commit. You can make the check required to gate merges on must-fix findings — but check what isn't reviewed first: a skipped PR gets no check at all, and a required check that never reports blocks the merge. |
Hyrax never merges its own pull requests, and by default its work always lands as a reviewable PR. (A repo can opt into a commit-direct mode where fixes land as commits on a branch you choose — see Fixes.)
Once a repo has PR review enabled, Hyrax reviews pull requests automatically as they're opened and updated, posting within a couple of minutes. On every plan, when CI fails on a Hyrax fix PR, Hyrax revises the change to get it green, bounded so it won't loop indefinitely.
Linear (tickets)
Hyrax can mirror your fixes into Linear so the work shows up where your team already tracks it. Linear is the only ticketing integration.
Setup
- An admin (or the account owner) connects Linear by storing a Linear API key in your workspace settings.
- Enable ticket config on the repositories where you want tickets created.
When you fix an observation on a ticket-configured repo, Hyrax creates a Linear ticket for that observation — titled with the finding's title, or with a ticket-title template you configure — and links it to the finding. When the fix PR opens, Hyrax adds the PR link as an attachment on that ticket, so the ticket and the fix PR reference each other — a clean trail from "Hyrax found this" to "here's the change."
New tickets land in the Linear workflow state you pick during setup, with the ticket's priority mapped from the observation's priority. After that, the ticket is yours to manage: beyond attaching the fix PR link, Hyrax doesn't move the ticket — closing, dismissing, or resolving the observation in Hyrax leaves the Linear ticket's state unchanged.
See also
- Pull request review — how automatic reviews work.
- Fixes — what gets turned into PRs and tickets.