v1.5.0
Code review finds its voice
Every finding siGit Code Review posts is now recorded, with a permanent link back to where it was said. This turns reviews into optional training data that can improve over time. Always off by default for siGit Code Pro users. Try it out for free!
siGit Code Review is:
- Alternative to CodeRabbit
- Alternative to GitHub Copilot Code Review
- Alternative to Greptile
- Alternative to Corgea
- Alternative to Qodo
- Alternative to Aikido Deep PR Review
- Alternative to Harness DeepSource
- Alternative to SonarQube
When a model fails in the middle of a review, the system automatically tries the next model in the same tier instead of giving up. You get your review, the model that failed gets investigated, and your bill stays the same.
Finding a voice
Every comment a code review posts now has a permanent identity. Not just the review itself, but each individual finding gets its own row in the database, with a link back to where it was posted.
This is the foundation for making reviews better over time. When someone thumbs-down a comment, or replies that a finding is wrong, or marks it as resolved, that feedback now has something to attach to. The system learns not just from what it said, but from what happened next.
Staying alive
When a model dies in the middle of a review—it's overloaded, it's down, it's just not responding—the system doesn't give up anymore. It automatically tries the next model in the same tier, at the same price point, until it finds one that's alive.
Your review still happens. Your bill doesn't change. The failed model gets logged for investigation. This is the difference between a system that works when everything's perfect and a system that works when reality hits.
The details that matter
The system is now honest about what it actually posted versus what it tried to post. When a review gets cut short because of a validation error, the count reflects what was actually said, not what was planned.
When GitHub's API changes how it returns data—like nulling out line numbers after a push—the system adapts. It matches comments by their original line number, which stays pinned to the exact commit the comment was written against, rather than a line number that might change.
This is infrastructure you don't see until it's missing. Now it's there, working quietly in the background, making sure your reviews land where they're supposed to.
Also, today is my birthday!