Pull request review
Review rules
Choose which pull requests TraceX reviews automatically, on which branches, with which trigger phrase, and add your team's own review rules.
Review rules decide when TraceX reviews a pull request and what it checks. Set them once for the organization, and override them per repository when one repository needs something different.
Open Pull requests → Review settings.
Organization rules
Section titled “Organization rules”| Setting | What it does |
|---|---|
| Review automatically | On: review pull requests by themselves. Off: only when someone asks. |
| Target branches | The repository’s default branch (usually main), all branches, or a list of patterns such as main, release/* (up to 20). |
| Review new pushes | Review again when new commits are pushed to an open pull request. |
| Trigger phrase | A comment phrase that starts a review now. @tracex review always works too. |
Choosing target branches
Section titled “Choosing target branches”- Default branch only suits most teams: every change headed for production gets a review, feature-to-feature merges don’t.
- Patterns suit release branches:
main,release/*,hotfix/*. - All branches reviews everything, which is noisier but catches issues earlier.
Per repository
Section titled “Per repository”A repository can follow the organization’s rules or have its own (on/off, branches, new pushes). Use this to switch automatic reviews off for a docs repository, or to review every branch on a critical service.
Custom review rules
Section titled “Custom review rules”On the Team plan, add your own rules and TraceX checks pull requests against them. Good rules are specific and checkable:
- “Every new database column must have a migration in
db/migrations.” - “Amounts are integers in cents. Flag any float used for money.”
- “Changes to
billing/need a test intests/billing/.” - “Never log a full request body in the payments service.”