Pull request reviews
TraceX reviews GitHub pull requests with the context of all your connected code, how the changed code is used in other services, and comments real defects on the exact lines.
Most review tools see only the diff. The bugs that reach production usually depend on what the diff doesn’t show: another service that calls the function you changed, a shared type whose meaning shifted, a file that was patched last week for the same reason.
TraceX reviews pull requests on connected GitHub repositories with the context of every repository your organization connected. Before it reviews, it looks at how the changed code is used elsewhere: callers in other services, shared types and API contracts, and recent changes to the same files. A change that is fine in its own repository can still break another one, and that’s what it’s looking for.
Ask for a review
Section titled “Ask for a review”Comment @tracex review on a pull request. Anyone with write access to the
repository can ask. Your organization can also set its own trigger phrase in
review rules; @tracex review always works. Reviews on request
are included in every plan.
Automatic reviews
Section titled “Automatic reviews”On Pro and Team, TraceX reviews every pull request automatically:
- when it is opened, reopened or marked ready for review,
- again when new commits are pushed (unless you turn that off).
Draft pull requests are never reviewed automatically. Each commit is reviewed once, so re-running CI doesn’t produce duplicate comments.
What TraceX comments on
Section titled “What TraceX comments on”Only real defects, each with the file, the line and the concrete failure:
- correctness bugs and behaviour that contradicts what the pull request says it does,
- security problems,
- data loss,
- missing error handling and race conditions,
- broken contracts with other services,
- anything your team’s custom rules ask for (Team plan).
It does not comment on formatting, naming or style. If there are no real defects, it says so in a short summary instead of inventing comments.
How the review appears on GitHub
Section titled “How the review appears on GitHub”- A GitHub review with inline comments on the exact lines.
- When the fix is a small change to that line, the comment includes a GitHub suggestion the author can apply in one click.
- Findings on lines outside the diff go into the review’s summary.
- The review is always a comment. TraceX never approves or blocks a merge; your branch protection and reviewers stay in charge.
See reviews in the dashboard
Section titled “See reviews in the dashboard”Pull requests lists the open pull requests on the project’s repositories and TraceX’s reviews of them.