v1.6.1

siGit Code Review used to write every review as if the change had never been looked at. The same finding would come back on the next push, on a line where someone had already hit resolve or replied "intentional, the caller checks"—and the thread nobody could end is what made an open pull request expensive to read.

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

#Answering the last review instead of repeating it

Before a review runs, it now reads the conversation already on the change: what it said last time, and what people said back. Each thread is labelled in plain words—settled, still unanswered, or outdated—and the rules that come with those labels are what stop a re-review from reading like a first look.

A settled thread can only be raised again by a diff that reintroduces or changes what it was about, and only by saying what changed. A finding that would land on the line of a settled thread is recorded but never posted, so outstanding feedback still keeps its line open. History is read only once a review is cleared to run, so a change that gets no review costs no extra call for history nobody will use—and on a forge that can't report its threads, a review runs exactly as it always has.

#Smaller fixes

• The phone menu now lists the same two products the desktop header does, instead of a longer, differently ordered list.
• The pull request and issue toolbars no longer run off the edge of a phone screen—the filters and action buttons stack and scroll instead of overflowing or breaking their labels apart.