Discover the latest features released in Gitar

Verification brings rule results, linked issue objectives, Knowledge, and cross-repo checks into one section below Code Review. 

Badges such as "Objectives 18/18" or "Rules 4/4 met" show the results. A section opens by default only when a rule fails or an objective is uncovered.

Cross-repo and Cross-PR coverage are grouped under Broader impact, with links to the inspected repositories and PRs.

Auto-apply criteria limit which review findings Gitar may fix automatically. 

Set organization criteria in Settings -> Configuration and extend them per repository with .gitar/config/apply.md.

Auto-apply still requires per-PR opt-in, and explicit fix requests work as before. 

Options in the dashboard comment shows how many findings were fixed and why the rest were skipped.

Agentic Security brings Sonar’s OpenAI Daybreak collaboration to Gitar. 

A change to an agent skill can remove a required approval step or leak credentials and private code. Gitar reviews the instructions and the scripts they call together to catch those risks.

Gitar catches a dropped sign-off step by comparing instruction versions. It inspects suspicious content without running it and validates each issue before posting a finding. Repository instructions cannot suppress these checks. Agentic Security is included with Enterprise.

Open Dashboard -> Agentic Security to browse critical and important security findings, with critical findings first. Select a count to see open or fixed findings, or repositories with open findings.

Gitar now checks related open PRs for changes that could break each other, within a repository or across connected repositories. For example, one PR might remove an API field that another still reads.

Findings carry a cross-pr label and link to the other PR. Browse them in Dashboard -> Cross-PR, labeled Cross-MR on GitLab. 

Cross-PR Analysis is on by default for Enterprise.

Risk Triage now assesses the whole PR as Low, Medium, or High risk, even when the review finds no defects. 

Define risk for the organization, add repository guidance, and use the result in approval and merge criteria. The assessment appears in the expanded Code Review section.

Catch a change that breaks another repository before it lands. 

The new Cross-repo dashboard shows affected repositories and recurring problems, with findings that explain which side needs a fix. Available on Enterprise, with connections discovered automatically.