Code Reviews

Use Code Reviews when you want Hacktron to review pull requests and comment directly on the pull request (PR). To get it running, connect GitHub, choose the repositories you want covered, and let Hacktron review qualifying pull requests.

​

What enabling code reviews does

After GitHub is connected, turn coverage on from the Repositories page. You can choose to cover PRs across all branches, or only to specific branches. If a repository is enabled and a PR is made, Hacktron checks if the PR’s target branch is configured. If it is, Hacktron reviews the PR. Hacktron comments on the PR with the vulnerabilities it finds, and provides quicklinks to fixing them with AI.

​

How to get started

1. Connect GitHub in Integrations
2. Open Repositories and choose which repositories should be covered
3. For each repository, choose which branches should be covered
4. Let your team keep working in PRs as usual
5. Review coverage and findings from the dashboard

You do not need to manually invite every developer before reviews can start. Hacktron can discover developers from repository activity as reviews begin running. If GitHub was skipped during onboarding, no PRs will be reviewed until the integration is connected and the repository is enabled.

​

If a PR is not being reviewed

Check these first:

• GitHub is connected in Integrations
• The repository is enabled in Repositories
• The organization still has review capacity available

If a developer is not covered, Hacktron leaves a PR comment explaining that no seat is assigned. It does not act like the review ran when it did not.

​

During the trial

For a new organization:

• The free trial lasts 14 days
• The trial begins when any organization owner adds payment information in Billing
• During the trial, Dev seats auto-assign as developers open PRs