Review agent pull requests with the clashes already found.
Agents open pull requests faster than people can read them. The gitta check compares every open pull request with the others, so reviewers see which ones touch the same code, and whether they pass your tests together, before they read a line.
Where review time goes
Each pull request passes its own tests. The trouble starts when two of them meet.
What your reviewers see.
One comment on each pull request, kept up to date, in plain words.
- 01These two break together
gitta merges both on top of the base and runs your tests. The comment shows what failed.
- 02These two change the same code
The newer one waits, and its agent updates it after the older one merges.
- 03This one is affected by that one
One changed something the other’s new code uses. Git merges it quietly, so this is the case a normal review misses.
Fits how your team reviews.
Nothing to set up for each agent. The check runs on the pull request events of your Git host.
- Cloud agents included
- Copilot coding agent, Codex cloud, Jules and Devin are checked like any other pull request.
- On GitHub, with more hosts coming next
- The check and its comment run on GitHub pull requests. GitLab and Azure Repos are coming next.
- Older work goes first
- When two clash, the newer one adapts. Two pull requests never block each other.
- Security findings in the same comment
- Risky code and weakened checks show up where the reviewer already looks.
- On the record
- Every merge, including an override, goes into the audit trail.
Show your reviewers how pull requests fit.
Add the gitta check to your repository and see the next batch of agent pull requests compared before anyone merges.
