Skip to main content

​
September 17, 2026

​
Knowledge that learns from the team

Gitar learns from review conversations and carries relevant guidance into later reviews, with citations back to its sources. Enterprise admins can now browse the library, inspect usage, and mark outdated entries stale in Dashboard -> Knowledge.

​
Cross-Repo Analysis is out of preview

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.

​
Azure DevOps Server and Bitbucket Data Center are generally available

Azure DevOps Server and Bitbucket Data Center are out of preview, joining the cloud integrations already out of beta. Connect from Gitar’s settings to bring reviews and automated fixes to self-hosted repositories.

​
Focus attention with Risk Triage

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.

​
Turn on automatic fixes with a label

Add gitar-managed to a GitHub PR or GitLab MR to enable automatic fixes for that change. Removing the label restores the configured default, and explicit per-PR settings still take precedence. Existing plan and usage limits apply.

​
Analyze Jenkins build failures

Connect Jenkins to have Gitar read failing build logs and explain the failure on the pull request. When Jenkins exposes stage logs or JUnit results, Gitar uses those to narrow the analysis. No Gitar plugin is required in Jenkins.

​
Connect YouTrack

Connect YouTrack Cloud or a self-managed instance. Gitar reads linked issues and checks their requirements against the change. Rules can create follow-up issues or update existing ones.

​
Connect multiple Azure DevOps instances

Manage multiple Azure DevOps connections in one Gitar organization, including cloud and Server instances. Each connection has its own credentials and project selection, so teams can work across instances from the same settings page.

​
Choose between Focused and Thorough reviews

Enterprise teams can choose review depth. Focused comments only where Gitar is confident the issue matters. Thorough includes smaller issues, with more comments to assess. Set the organization default in Settings -> Configuration, then override it per repository where needed.

​
Reviews understand stacked changes

On GitHub and GitLab, Gitar now receives review context about open changes stacked after the one under review. It can account for work planned in a later PR when judging whether the current change is incomplete.

​
Reuse existing agent instructions and skills

Gitar now reads repository instructions from .claude/rules alongside .cursor/rules and discovers skills in .agents/skills. Keep guidance and reusable skills in the locations the team’s coding tools already use, including in the shared configuration repository.

​
Clearer setup and feature documentation

The documentation now includes a platform support matrix, with corrected connection steps and less repeated guidance across feature pages. Check what each platform supports and follow the setup path for cloud or self-hosted repositories.

​
Usability improvements

  • Enterprise admins can enable Knowledge and Cross-repo independently from their dashboards. New Enterprise organizations get both enabled by default. Disabling either stops future processing and retains its history.
  • The expanded Code Review section shows review coverage, so the scope of Gitar’s investigation is visible beside its findings.
  • GitLab setup checks webhook delivery, with setup guidance available from connection settings.
  • Azure DevOps now honors gitar-skip for code review and rule evaluation.
  • Manage Bitbucket Data Center repositories from the configuration page, including refreshing repository discovery and webhooks.
  • Hover over category and repository tables in the Reviews dashboard to see the breakdown behind each total.
  • Rule results are grouped by their authored rule file, and the dashboard footer summarizes rules that did not apply.
  • Filter Gitar Activity by repository to focus Insights on the projects that matter.
  • Refresh Bitbucket Cloud repositories on demand, and resume an interrupted connection flow without starting the installation again.
  • Jenkins and YouTrack credentials are checked before they are saved.

​
Bug fixes

  • Approval decisions are re-evaluated after code or policy changes. A previous approval or rejection no longer survives after its supporting evidence changes.
  • Findings targeted by a requested fix stay open when the fix cannot be pushed, preventing approval based on a change that never reached the branch.
  • An incomplete review no longer produces an approval just because it recorded no findings.
  • Rebases no longer bring unrelated upstream changes into the review diff.
  • Applying a suggested fix preserves overlapping changes that the author already explained or asked Gitar to keep.
  • Suggested fixes that are identical to the code they replace are no longer offered.
  • GitHub review checks no longer remain stuck running after Gitar finishes.
  • Resuming a comment conversation restores the current CI analysis instead of incorrectly reporting that no failures were detected.
  • Buildkite and Bitrise failure events now reach CI analysis.
  • Auto-merge reporting now reflects whether the platform accepted the request, including when Gitar pushed a fix during the review.
  • Azure DevOps reviews now read changes beyond the first 100 files.
  • GitLab merge-blocking detection checks the merge request’s actual state, avoiding incorrect reports that a merge is blocked.
  • Disconnecting an Azure DevOps, GitLab, or Bitbucket Data Center connection no longer cancels work on unrelated connections. Repository discovery also preserves disconnected Azure repositories.
  • Bitbucket Data Center respects the setting to skip draft pull requests, and commits made through service-account connections are signed.
  • Automatic fixes select the correct repository when multiple connections contain repositories with the same name.
  • LiteLLM connections now use the gateway’s configured model routing and credentials.
  • Insights repository filters no longer fail when the selected repository list is too large for a URL.

​
August 28, 2026

​
Bring your own model

Run every LLM call for your organization on your own account. Open Settings -> Configuration -> Bring Your Own Model and pick a provider: an Anthropic API key, an AWS Bedrock role, or a gateway you run through LiteLLM, Portkey, or OpenRouter. Gitar still picks the model for each task. You pick the account those calls are served from and the region they run in. Bedrock adds a residency geography, a cross-region inference toggle, and an optional guardrail that Gitar sends on every call, so PII masking you configured applies. Test connection invokes each provider before saving, so a role that cannot reach a model fails at setup rather than on your next review. Enterprise plan. Bring Your Own Model

​
Connect Harness and TeamCity

Harness and TeamCity join Buildkite, CircleCI, and Bitrise as connectable CI providers. Give Gitar a token that can read builds, and it downloads the log for each failing build and analyzes it. See Harness and TeamCity.

​
Share skills, rules, and review instructions across repositories

Name one repository as your organization’s configuration repository, and every other repository inherits its .gitar/ directory: skills, rules, review instructions, and agent instructions. A repository’s own copy of a skill or rule wins over the inherited one, so a team can override a central default. Set the repository at the foot of the Repositories card in Settings -> Configuration. Pro and Enterprise plans, rolled out per organization. Configuration Repository Skills are new in this release too. A skill is a SKILL.md of instructions your rules or PR comments call by name, versioned with your code, and it can ship scripts for the agent to run. Gitar loads a skill into the calling agent’s own turn with that agent’s full toolset. Skills

​
Functional validation reads every issue source

A PR that links a GitHub issue, a GitLab issue, an Azure DevOps work item, a Bitbucket Cloud issue, or a Plane work item now gets the same Implementation Status block that Jira and Linear already had. Gitar reads the issue, splits it into objectives, judges each one against the diff, and re-judges on every push. On a code host with its own tracker, Fixes #123 is enough. Turn it off with the Functional validation toggle on the configuration page. Enterprise plan. Functional Validation

​
Custom integrations are now MCP endpoints

A custom integration is an https MCP server URL. Supply the endpoint, name the HTTP headers your credentials travel in, and list which tools the server may expose. Custom Integrations (MCP)

​
Track work in Plane

Plane joins Jira and Linear as a work item source, on Plane Cloud and on self-hosted instances. Gitar reads the work items a PR links, and your rules can have it search, create, update, comment on, and transition them. Plane

​
Choose which branches Gitar reviews

Two scope settings, Allowed target branches and Excluded target branches, filter PRs by the branch they merge into. Both take names or globs such as main or release/*, and the exclude list wins. Teams on a stacked branching model can put main,release/* in the allowed list to keep Gitar quiet on intermediate merges and review only the merge that matters. The filter applies on GitHub, GitLab, Bitbucket, and Azure DevOps. Target branch patterns

​
More platform coverage

Azure DevOps and Bitbucket are out of beta. Self-hosted has guides of its own. Azure DevOps Server and Bitbucket Data Center cover the inbound reachability and webhook egress an on-premises server needs. GitLab self-hosted Free edition is now supported. GitLab

​
Usability improvements

  • Auto-merge takes criteria. Write your merge conditions in plain language and Gitar evaluates them in the same pass as auto-approve, or commit .gitar/config/merge.md to set a policy per repository. Require the per-repository file and a repository without one is never armed. Auto-Merge
  • The dashboard comment says why a PR was not armed for auto-merge, instead of leaving you to guess.
  • Steer the prose Gitar writes under the Code Review header with Review summary instructions in settings. Leave it empty for the current default.
  • Bitbucket Cloud and Data Center share one connect entry with Cloud and Server tabs, in settings and in onboarding, and the Connections card lists every connected Cloud workspace with a link to add another.
  • Integration cards prefill their stored configuration when reopened and show which secrets are already set.
  • Jira Cloud runs over the Gitar Forge app instead of 3LO OAuth, so Gitar can create, update, comment on, transition, and link issues while holding no Atlassian credential of its own. Existing installs need an admin to re-approve consent.
  • On Azure DevOps, only the newest auto-approve notice survives, rather than one stacking per commit.
  • The Confluence card lists which spaces the Gitar app can read, per site, and shows a distinct state when the app is installed but no space has been shared with it yet.
  • A ticket key in the title position, such as [ENG-1] Add pagination, links to that ticket on its own, with no Fixes keyword needed.
  • Enterprise organizations have an in-product support widget.
  • Organization slugs that would collide with a Gitar route are rejected at create and rename, instead of returning 404 on every page in the organization.
  • Community links point to the Sonar community rather than Discord.

​
Bug fixes

  • Gitar posts fewer, cleaner comments. The dashboard comment updates in place instead of reposting on every run, which was notifying everyone on a PR each time, and it stops rolling once a PR is closed or merged.
  • Review output reads correctly. Findings are no longer cut off mid-code, code in a finding no longer breaks the formatting of the rest of the comment, and the summary can no longer claim a change introduced no regressions on a review that found nothing.
  • Gitar is accurate about merge state. It no longer says a merge request is blocked when anyone could merge it.
  • CI analysis stays current. A failure already fixed on an earlier commit is not reported again, and the analysis no longer disappears from the GitLab dashboard comment moments after it posts.
  • Webhook delivery is correct on GitLab and Bitbucket. GitLab organizations no longer receive every event twice, a disconnected organization stops delivering, Bitbucket honors skip_draft_prs, and a busy Bitbucket repository no longer drops its own CI events.

​
August 7, 2026

​
Gitar is free for open source

Public repositories with an OSI-approved license on github.com or gitlab.com can now use Gitar for free, with the full Pro feature set and no seat limits. Apply from the plans page and we’ll review your project.

​
Connect more than one GitLab instance

Settings → Configuration has a new Connections panel that lists every supported code host and every connection underneath it, replacing the single connect button per platform. GitLab can now hold several instances at once, so you can run a self-hosted instance and gitlab.com side by side - useful while migrating between them. Each connection shows its own health, account, and repository count, and can be managed or disconnected on its own without touching the others. When a service account token is about to expire, the warning appears on just the instance it belongs to.

​
Custom integrations (MCP)

Custom integrations let you extend Gitar with your own tools. Alongside the built-in integrations, you can register an MCP server, or a set of plain instructions, and Gitar’s rules and agents can use it while reviewing pull requests and running automations. Configure the environment variables your server needs, store API tokens as org-scoped secrets that are injected at runtime, and point at a private package registry if your server is published to one. Custom integrations are an Enterprise feature. Custom Integrations (MCP)
Superseded: instructions-only integrations, environment variables, and private registries have since been removed. A custom integration is now an https MCP server URL. For instructions with no server, use Repo Skills.

​
Usability improvements

  • Connecting a GitHub organization or GitLab group with thousands of repositories or projects is now a much smoother experience, with a background process that imports them asynchronously.
  • The repository list has a filter for repositories that aren’t enabled, so it’s easier to find ones Gitar isn’t watching yet.
  • Auto-merge can now be set per repository. Like auto-approve, you can turn it on for one repository and off for another, and a repository override that only changes the on/off switch still inherits your organization’s merge method.
  • When branch protection or a repository ruleset rejects Gitar’s push, Gitar now explains that on the pull request once, instead of failing silently and retrying.
  • Inline threads close themselves. If you ask Gitar for a change in an inline comment and it pushes the fix, the thread is resolved automatically on GitHub, GitLab, Bitbucket, and Azure DevOps.
  • Azure DevOps caught up on the rest of the workflow: gitar unblock, CI failure analysis and retry for Azure Pipelines, an auto-merge method picker, selecting multiple projects at install and connecting or disconnecting them individually afterward, and an inline banner when your PAT has expired.
  • Bitbucket now supports multiple workspaces under one organization, re-reviews on new commits, reads Bitbucket Pipelines logs, handles fork pull requests, and emails and Slacks your admins if the installation goes unhealthy.

​
Bug fixes

  • Reviews no longer flag code the pull request didn’t touch. A stale base reference could pull already-merged commits from the base branch into the diff, which showed up as findings against changes you never made.
  • Force-pushing a branch no longer triggers a full re-review of the whole pull request. Gitar now reviews only what changed since its last review.
  • The Gitar dashboard comment now posts reliably on GitLab merge requests. It could previously loop forever and never appear, even though inline findings and the summary posted normally.
  • Findings are no longer marked resolved unless the fix actually reached the remote, so a pull request can’t be approved on the strength of a commit that was never pushed. Conversely, a push that had nothing left to do no longer leaves findings stuck open.
  • Reacting with the checkmark emoji to apply a fix now works on newly connected GitLab organizations. The webhook Gitar needs for emoji reactions wasn’t being requested at setup.
  • CI Fixer no longer reports CI as green when it isn’t.
  • gitar unblock now respects repository-level setting overrides instead of only reading your organization defaults.
  • Fixed a Stripe timing bug that could drop a paying organization back to the Free tier immediately after converting from a trial.
  • The Rule Catalog header count now matches the totals shown in each category.

​
June 26, 2026

​
Azure DevOps and Bitbucket support (Beta)

Azure DevOps and Bitbucket support are in beta. Expect rough edges as we round out coverage. We’d love your feedback.
Gitar now works with Azure DevOps and Bitbucket repositories. Connect them right from onboarding alongside GitHub and GitLab, and Gitar posts reviews, PR summaries, and dashboard comments and responds to interactive commands on those pull requests. Connected repos and pull requests show the right platform logo throughout the web app (recent activity, settings, and repo lists), with an “Open in Azure DevOps” / “Open in Bitbucket” link.

​
Faster responses to your activity

Gitar now reacts immediately to the events you care about (PR/MR opens and closes, comments, pushes, accepted fixes, and enabling auto-apply) instead of waiting out a batch delay, so it feels noticeably more responsive. Only bursty machine signals like CI-failure floods and metadata edits are still batched.

​
Usability improvements

  • Repository search in your settings is faster and more accurate. Results are ranked by relevance so exact and prefix matches surface first, and a new “All organizations” dropdown narrows the list to a single owner when you have repos across multiple organizations.
  • Pro orgs now get double the per-seat review budget, so upgrading from Core translates into tangibly more automated reviews before any pause kicks in.
  • When you reply to a finding by proposing or comparing an alternative (“what about exit 1 instead?”), Gitar now treats it as a question rather than an instruction to change code. It only applies and commits a change once you explicitly tell it to.
  • Add your own notes below Gitar’s PR summary and they stay put. The summary is now a self-contained block that Gitar updates in place, so anything you write underneath it, and any edits you make to the rest of the description, is preserved across summary updates.
  • Clearer messaging when you hit a limit. Rate-limit replies now tell you roughly how long to wait before retrying, and when Gitar pauses automatic reviews it now explains that you can still run Gitar review manually in the meantime.

​
Bug fixes

  • Auto-merge failures are now surfaced instead of silently claiming the PR is armed. If your platform rejects enabling auto-merge (repo setting off, missing permission, or nothing to wait on), Gitar tells you the actual reason.
  • PR summaries no longer mix in unrelated changes pulled from merging main into your branch. Summaries focus only on the PR’s own contributions.
  • More consistent review verdicts across pushes: Gitar now retains awareness of findings you’ve already resolved or dismissed when re-reviewing, so a PR no longer flip-flops between Approved and Changes Requested.
  • Resolving all open finding threads now correctly dismisses Gitar’s blocking review and clears the check, so the PR becomes mergeable the moment you’ve addressed every finding.
  • Auto-approve now re-applies after you push to an already-approved PR. A clean re-review correctly re-approves instead of leaving the PR stuck without approval.
  • Allow-listed bots now work independently of other event-filter lists, so adding just Dependabot (including bot names with periods) gets those PRs reviewed. The manual “Start Review” button also works on bot-authored PRs.
  • CI failure analysis now persists across dashboard comment reposts instead of vanishing when a new commit refreshes the comment.
  • Findings with blob-URL sources now anchor as inline comments on the affected lines instead of appearing only in the summary.

​
May 11, 2026

​
One-click apply fix from inline comments

When Gitar suggests a fix in an inline review comment, you can now apply it in one click. On GitHub, check the box next to the fix. On GitLab, react with the corresponding emoji. Alternate checkmark emojis are also accepted. Gitar commits the fix to your branch. When a finding has multiple fixes, each one is numbered so you can pick the right one.

​
gitar unblock on GitHub

The gitar unblock command now works on GitHub PRs in addition to GitLab MRs. Comment gitar unblock to dismiss Gitar’s blocking review and ungate merging. The hint only appears in review comments when Gitar is actually blocking the PR.

​
gitar-approved label

When Gitar auto-approves a PR, it can now apply a gitar-approved label to make approved changes easy to filter in your platform’s PR list. Enable the label from the “After approval” section of your auto-approve settings.

​
New insights

Resolution by Author. The Reviews dashboard now shows review effectiveness per author: PRs reviewed, findings reported, resolution rate, and a Top/Bottom 5 toggle for surfacing outliers.

​
Auto-approve works without custom criteria

Auto-approve no longer requires explicit criteria to take effect. When the toggle is enabled and no criteria are configured, neither in your org settings nor in a .gitar/config/approve.md file, Gitar will approve PRs automatically when all code review issues are resolved. If you want to restrict which PRs are auto-approved (for example, only docs changes, only small PRs), set custom criteria in your org settings or add a per-repo approve.md file. See Auto-Approve for details.
If you previously had auto-approve enabled without criteria, your PRs were not being auto-approved. With this change, those PRs will now be auto-approved when the code review passes. Review your auto-approve settings if this is not desired.

​
Usability improvements

  • Finding badges for Gitar fixer-resolved comments now show the commit SHA, for example “Fixed in abc1234 by @user via Gitar”, so you can see exactly which commit contains the fix
  • PR summaries now augment on new commits instead of replacing. Earlier commit descriptions are preserved across the full PR lifecycle

​
Bug fixes

  • Improved code review accuracy: fewer false rejections on findings near changed code, faster feedback visibility, better responses to finding questions, and re-evaluation when PR metadata changes
  • Auto-approve now works correctly on draft PRs when your criteria allow it
  • “Fixed in SHA” badge no longer appears on dismissed findings
  • Stale CI analysis findings are now cleared when the fix commit passes CI
  • Draft-to-ready PR transitions now correctly trigger rule evaluation
  • gitar unblock on GitLab now deletes the blocking comment instead of leaving it behind
  • Fixed MRs by Type chart filter mismatch with MRs Processed metric on GitLab
  • Settings sidebar padding and mobile gap fixed

​
April 24, 2026

​
Auto-merge after auto-approve

When Gitar auto-approves a PR or MR, it can now arm your platform’s native auto-merge at the same time. As soon as CI turns green and required approvals land, the change merges itself. Enable it from your organization settings.

​
Per-repo auto-approve criteria

Drop a .gitar/config/approve.md file in any repo to set auto-approval rules for that codebase. They’re appended to your org-level criteria.

​
Scoped configuration settings

We rebuilt the configuration page around org and repo scopes. The org view is where you set defaults for everything (skip draft PRs, block merges, auto-approve, auto-merge), all in a single Behavior card with help popovers for each control. When you need a repo to behave differently, open its overrides dialog. It shows what’s different from the org default and lets you reset any override in one click.

​
New insights

Tech Debt Over Time tracks ignored vs. resolved findings over time on the Reviews dashboard. PRs by Type splits your review activity by PR kind, including features, fixes, and refactors, on the Insights Overview. Plus a few smaller insights changes:
  • Interval selectors: Daily / Weekly / Monthly grouping on both the Reviews and Insights dashboards, defaulting to Weekly to smooth out weekend dips
  • Sortable Resolution by Repository: click any column (PR count, Reported, Resolved, Rate) on the Reviews widget to sort, with the Top/Bottom 5 toggle following the active sort
  • Approved badge: Recent PRs view marks reviews that completed with zero findings with a green “Approved” check

​
GitLab improvements

​
GET /v1/external/gitlab/mr_status endpoint

If your GitLab setup restricts approval-rule APIs, you can now hit a new endpoint to get Gitar’s blocking status for an MR (blocked: yes | no | pending) and gate merges with a CI job instead.

​
gitar unblock auto re-triggers the pipeline

After gitar unblock runs, the GitLab pipeline is retriggered automatically so gitar-check picks up the updated status. No need to manually re-run.

​
Project rename handling

Renaming a GitLab project no longer silently stops reviews. Gitar listens for the project_rename system hook and updates stored paths on the fly.

​
Bug fixes and usability improvements

  • Bulk enable/disable repos during onboarding and in repository settings
  • New external API endpoint to onboard GitLab projects programmatically
  • GitLab webhook validation now lives inline in the GitLab connection dialog with per-project “Validated” / “Webhook Missing” badges
  • GitLab PAT validation runs at install and on updates with a clear timeout. Rotating to a new service-account PAT immediately re-resolves the bot username. The GitLab connection dialog drops the unused OAuth tab
  • Fork PR pushes: Gitar now pushes fixes to forked PRs when the author has enabled “Allow edits from maintainers” (GitHub) or “Allow commits from members who can merge” (GitLab), and posts a clear comment explaining what to enable when it can’t
  • gitar unblock quality-of-life: accepts trailing punctuation, nests visibly under merge blocking in settings, and the hint in review comments only shows when Gitar is actually blocking
  • Disabling draft-PR reviews, PR summaries, or CI retries in settings now reliably applies regardless of which webhook triggered the review
  • Gitar Fixes preserves tab indentation in tab-indented files (Go, Makefiles), rules with frontmatter scoping only evaluate on relevant files, and PR summaries work on PRs with empty bodies

​
April 7, 2026

​
On-demand processing of changes

You can now configure per-repo whether Gitar processes every change automatically or only on demand. When on-demand is enabled, Gitar will only act when addressed directly via a comment, for example gitar review or gitar fix this please.

​
Skip draft PRs

A new toggle in organization settings lets you skip draft PRs and MRs entirely. When enabled, Gitar ignores drafts until they are marked ready for review. Comments on drafts are still processed.

​
Onboarding: connect your issue tracker

The onboarding flow now includes a step for connecting Jira or Linear. You can set up your issue tracker and configure automation rules without leaving the setup wizard.

​
GitLab improvements

​
gitar unblock command

On GitLab, users with the Developer role can’t remove a reviewer through the UI, so there’s no way to dismiss Gitar’s blocking review when you need to merge urgently. Comment gitar unblock on any MR to dismiss the blocking verdict and ungate merging. Works on both standard and enterprise installations. Admins enable the command from organization settings.

​
Token updates and project disconnect

  • Service account token updates: Update your GitLab service account PAT directly from the configuration dialog when it expires or needs rotation, without disconnecting the installation.
  • Project disconnect: Disconnect a GitLab project directly from its configuration page, with a confirmation step.

​
Other GitLab improvements

  • Force push detection: Gitar now detects force pushes on GitLab MRs, ensuring reviews, findings, and ticket metadata stay accurate after history rewrites
  • Service account mentions: Gitar responds to mentions of custom GitLab service accounts (for example, @gitar-service-yourorg), not just the default bot account
  • Inline comment deduplication: A retry loop that could create duplicate inline comments on API errors has been fixed

​
Usability improvements

  • Improvements to the auto-approve flow for more accurate approval decisions
  • Free-tier organizations see an upgrade prompt in Gitar’s dashboard comment
  • Gitar reacts with +1 on your comment after processing an integration request (Jira, Linear, Slack), so you know it went through
  • Auto-apply badge colors adjusted for better visibility in light mode

​
Bug fixes

  • Findings on unchanged context lines (for example, pre-existing code visible in the diff) are now correctly dropped instead of blocking the PR
  • Reviews only cover code the PR actually changes, even after merging the target branch into a feature branch
  • GitLab auto-approve no longer re-adds the bot as reviewer after you manually dismiss a blocking review
  • Improved handling of force pushes: findings and review state update correctly after history rewrites
  • Threaded replies on PRs now consistently land on the correct comment

​
March 31, 2026

​
Integration health monitoring

The dashboard now shows notification cards when your Jira or Slack integrations become unhealthy, with specific messages about what went wrong, including a revoked token or an uninstalled app. Cards link directly to settings so you can fix the issue. BYOK users also see an alert when their API key returns authentication errors, with automatic recovery once the key works again.

​
GitLab in-place token updates

You can now update your GitLab access token directly from the GitLab dialog without disconnecting and reconnecting the installation. If Gitar detects that your token is invalid or expired, a banner prompts you to enter a new one. You can also proactively rotate your token at any time from the same dialog.

​
Respond to Gitar in dashboard comments

Replies to Gitar’s dashboard comments on your PRs are now treated as first-class interactions. Gitar reads your reply, reviews the relevant context (CI results, findings, rules), and responds directly in the thread.

​
Billing improvements

  • Confirmation dialogs for plan changes now show inline price breakdowns so you can see the cost impact before confirming
  • You can switch from annual to monthly billing, scheduled for your next billing cycle
  • “Contact Sales” buttons for Enterprise show a dialog with the email address and a copy button, instead of relying on mailto: links that fail silently

​
Co-author attribution fix

Gitar commits from auto-apply now correctly attribute the PR author as a co-author on GitHub and GitLab. Previously, bot and GitLab user actors were not resolved, resulting in commits with no co-author line.

​
March 24, 2026

​
GPG-signed commits

All commits pushed by Gitar are now GPG-signed. Repos with branch protection rules requiring verified commits no longer need an exception for Gitar.

​
Clarification on ambiguous finding replies

When your reply to a finding is ambiguous, Gitar now asks a follow-up question instead of guessing. Fewer false dismissals, fewer wasted fix attempts.

​
CI retry controls

CI retry has its own toggle in organization settings. Gitar now retries CI when any failure is unrelated to the PR, instead of requiring every failure to be unrelated. One flaky test no longer blocks retry of the whole suite.

​
GitLab improvements

​
Automatic approval rule setup

When merge blocking triggers on a GitLab MR, Gitar automatically creates the required approval rule.

​
Service account token requirement

GitLab installations now require a service account token instead of a personal access token. Gitar operates under a dedicated service identity rather than a personal user account.

​
Dedicated sign-up page

GitLab users get their own sign-up page tailored to the GitLab workflow.

​
Multiple GitHub installations

Organizations can now connect multiple GitHub App installations for multi-account setups.

​
Usability improvements

  • Dashboard polish: escaped @mentions in comments, clearer subscription badges, consistent findings counts
  • Better GitLab support in seat management and CI analysis output labels
  • PR summaries respect the org-level dashboard toggle (disabling it actually disables summaries now)
  • “Last month” date preset on the Insights page
  • Simpler API token creation dialog

​
Bug fixes

  • Inline comments handle GitHub rate limits, large diffs, and GitLab 429 errors more gracefully
  • Dismissed and resolved findings now sync correctly across the review report, dashboard, and platform threads
  • More accurate stale finding classification after force-pushes and on newly added code
  • Auto-apply no longer defaults to the org entitlement instead of off
  • GitLab blocking reviews and cross-platform dismiss override tracking
  • Suggested fix breaking dashboard comment formatting
  • 500 error on seat update for trialing and paused subscriptions
  • Infinite loop when CI log fetch fails
  • Merge-commit diff pulling in unrelated changes from main branch
  • Jira OAuth refresh token race condition
  • Orphaned GitHub comments for deduplicated findings
  • Cherry-picked no-op files appearing in PR diff
  • Transferring a GitHub repo between orgs
  • Code review not running on comment events
  • Commit messages showing generic “Changes by Gitar” instead of describing actual changes
  • Email addresses not showing in Audit Logs fallback

​
March 2, 2026

​
Smarter Code Reviews

​
Reviews Tab

The dashboard has a new “Reviews” tab with code review metrics, replacing the previous Insights sub-page.

​
Review Thread Sync

Resolving or unresolving a finding thread on GitHub or GitLab syncs the finding state in real-time. Resolve a thread and the finding is dismissed from the review report. Unresolve it and the finding reopens. On GitLab, you can also thumbs-down a finding to dismiss it.

​
Feedback That Actually Works

Replies like “this is intentional” or “already done” on findings are properly processed and dismiss the finding, even without new commits. Previously, these responses could be silently dropped.

​
Stale Findings Auto-Resolved

When code is deleted or rewritten between review iterations, Gitar automatically resolves findings that pointed at the removed code.

​
Better Reviews on Large PRs

On large pull requests, Gitar prioritizes high-value source files and summarizes low-signal files like generated code and lockfiles.

​
Copy Findings as Prompt for Agents

The review comment includes a collapsible “Prompt for agents” section with all findings as plain text. Copy and paste into your LLM, Slack, or editor without HTML formatting getting in the way.

​
Inline Fix Call-to-Action

Inline review comments include a “Reply gitar fix to apply this suggestion” footer. One reply and Gitar applies the fix.

​
Less Noise in PR Threads

Gitar only responds to comments directed at it. Conversations between teammates no longer trigger unwanted replies.

​
Faster, Quieter CI Failure Analysis

Identical failures across multiple jobs are detected and analyzed only once. CI events for outdated commits are ignored after you push new code.

​
Billing & Seats

​
Per-Seat Licensing

Team-tier organizations enforce per-seat licensing. Users without an active seat see a notice when they invoke Gitar commands. Org admins can manage seats from the billing page, and during checkout all org members are pre-selected so you can review and adjust before purchasing.

​
Redesigned Upgrade Flow

Seat selection is the first step when upgrading from Free or Free Trial to Team. The confirmation dialog and error states have also been cleaned up.

​
Outside Collaborators in Seats

GitHub outside collaborators appear in the seat management view alongside org members, with a “Collaborator” badge.

​
GitLab Member Autocomplete

GitLab group members are searchable and selectable during checkout, matching the GitHub autocomplete experience.

​
Seats View Overhaul

The seats page groups users into three tiers: seated, active without a seat, and inactive.

​
Email Notifications

Org admins receive email notifications when their trial is ending and when their subscription activates.

​
New Configuration Options

​
PR Summary Toggle

Org admins can enable or disable PR summary generation from the settings page. Enabled by default, and also configurable during onboarding.

​
Multiple Commands in One Comment

You can now include multiple gitar commands in a single PR comment. For example, write gitar auto-apply:on and gitar display:verbose on separate lines and both will be processed. Last-wins semantics apply for conflicting instructions.

​
Auto-Apply Simplified

Auto-apply is now controlled per PR using the gitar auto-apply:on/off command.

​
Usability Improvements

  • PR summaries are posted immediately when ready instead of waiting for all processing to complete
  • Gitar reviews its own pushed fix commits to catch issues before you see them
  • GitLab users can now reply to Gitar’s inline findings without needing the “gitar” prefix
  • When a trial converts to paid, usage counting starts fresh from the upgrade date
  • Trial upgrade footer now only appears in the final 7 days of your trial
  • Free-tier organizations now see an upgrade prompt on the dashboard
  • New “Join Discord” card on the dashboard for community access

​
Bug Fixes

  • Fixed duplicate findings appearing across files
  • Fixed auto-apply not respecting PR-level overrides (for example, gitar auto-apply:off was ignored)
  • Fixed inline code spans with newlines breaking markdown rendering in review findings
  • Fixed inline comment threads on GitHub not resolving when findings were marked resolved
  • Fixed GitLab inline comments never being resolved due to missing discussion IDs
  • Fixed duplicate Gitar comments on GitLab caused by transient HTTP 500 errors
  • Fixed Gitar not recognizing past-tense confirmations like “this was fixed” or “it has been fixed”
  • Fixed GitLab self-comment loop where Gitar could process its own inline finding comments
  • Fixed GitHub check runs stuck as “running” after failed or idle executions
  • Fixed reviews failing on files with extremely long lines (for example, protobuf or base64 blobs)
  • Fixed processing failures on repositories with very large instruction files
  • Fixed fork PR co-author detection failing on GitHub
  • Fixed GitLab PAT connection from settings skipping the project selection step
  • Fixed trial end dates persisting incorrectly when Stripe subscriptions changed status
  • Fixed billing page not showing price for users without a subscription
  • Fixed trial upgrade footer missing for Team-tier orgs with active trials
  • Fixed false “No Code Hosts Connected” notification flashing during page load

​
February 16, 2026

​
Usability Improvements

  • Faster code review feedback through optimized review pipeline
  • Auto-apply now fixes code review findings in addition to CI issues
  • Gitar no longer re-blocks a PR after you dismiss a blocking review

​
Bug Fixes

  • Fixed inline comment formatting issues causing malformed output
  • Fixed inline comment resolution skipping findings
  • Fixed Jira integration not fetching ticket context for some organizations
  • Fixed GitHub check run spinner not appearing after pushing new commits
  • Fixed onboarding retry failures caused by stale state
  • Fixed code review findings not being dismissable as false positives
  • Fixed dashboard display issues
  • Fixed race condition when a PR is merged while Gitar is working
  • Fixed Gitar not refreshing dashboard comment when commands like “gitar auto-apply:on” are issued

​
February 10, 2026

​
Usability Improvements

  • Better progress updates: Gitar now shows “Responding to your feedback” instead of generic “working” status
  • Mobile-responsive settings pages with collapsible sidebar
  • Insights page now counts metrics by business days for more accurate averages
  • GitLab users can now paste a full project path (for example, group/subgroup/project) during onboarding to find their project instantly.
  • Gitar now responds appropriately when you reply to a finding with “this is intentional” instead of misinterpreting it as a fix request

​
Bug Fixes

  • Fixed code review findings not being updated after fixes from commits/user feedback
  • Fixed duplicate dashboard comments caused by concurrent updates
  • Fixed self-hosted GitLab URL issues, OAuth, and webhook handling
  • Fixed inline comments appearing on wrong lines
  • Fixed Gitar rules not executing on the first PR review
  • Fixed duplicate blocking comments on GitLab merge requests
  • Fixed code review failures on PRs that are closed immediately after opening
  • Fixed outdated inline comments appearing after pushing new commits
  • Fixed GitLab markdown-formatted commands not being recognized
  • Fixed member removal in Settings when users weren’t on the first page
  • Fixed deleted dashboard comments causing repeated update failures

​
January 29, 2026

​
New Configuration Options

​
Label-Based PR Filtering

Configure pull request labels on repositories so Gitar only processes PRs that have matching labels. This gives teams fine-grained control over which PRs Gitar should review. When a matching label is added to an existing PR, processing triggers automatically.

​
Configurable PR Merge Blocking

Gitar can now automatically block PR merges based on code review verdict severity. Configure a threshold in Code Review Settings:
  • Approved
  • Approved with Suggestions
  • Changes Requested
  • Blocked
When Gitar’s verdict meets or exceeds the configured threshold, it submits a blocking review to prevent merging until issues are addressed.

​
User Filtering for Inline Comments

Org admins can now restrict inline code review comments to specific team members. Other users’ PRs will receive top-level comments only, enabling gradual rollout of inline comments.

​
Code Review Improvements

​
@gitar Prefix Support

You can now invoke Gitar in comments using @gitar as a prefix in addition to gitar. Both formats work identically across GitHub and GitLab:
  • gitar fix this bug
  • @gitar fix this bug

​
Enhanced Rule Recommendations

Rules now provide more structured, actionable feedback:
  • Not Met: Actionable recommendation (for example, “Add labels to this PR”)
  • Met: Brief explanation of what satisfies the requirement
  • Not Applicable: Why the rule doesn’t apply to this PR

​
Usability Improvements

​
Progress Updates While Working

Gitar now shows meaningful progress updates while processing your requests, so you can see what’s happening in real-time.
  • Faster initial code review for quicker feedback
  • Code review remembers your feedback on previous findings and won’t re-report dismissed issues
  • Refreshed dashboard theme with updated colors and improved chart styling
  • Sign in with GitLab
  • Simplified onboarding steps

​
Bug Fixes

  • Fixed various issues with OSS repositories that receive contributions from forks
  • Fixed issues with new user sign-ups
  • Fixed self-hosted GitLab checkout failures
  • Fixed binary file handling for ZIP, XLSX, DOCX files

​
January 19, 2026

​
Try Gitar on Your Open PRs

New users can now try Gitar instantly on their existing pull requests. When getting started with Gitar, the dashboard displays a card showing your recent PRs with a “Start Review” button to kick off a code review with one click.

​
Code Review Insights Dashboard

View aggregated unresolved code review findings across all your repositories, grouped by category. This new Insights section helps teams identify recurring patterns and common issues in code reviews to improve overall code quality.

​
Organization Settings Page

Administrators can now manage organization name and logo from a dedicated settings page.

​
Improved Onboarding Experience

The onboarding flow has been completely redesigned:
  • Visual step indicators with progress tracking
  • Mobile-optimized layouts with responsive design
  • Shorter flow with optional organization setup

​
Usability Improvements

  • Faster response times and reduced processing overhead
  • Code review comments now land on the correct lines
  • Mobile navigation improvements

​
Bug Fixes

  • Fixed issues where some code review comments were duplicated
  • Fixed GitLab inline comment failures that caused intermittent posting issues
  • Fixed race condition where stale CI analysis could display after pushing new commits
  • Fixed auto-apply race condition when users enable it mid-execution
  • Better support for reviews on PRs targeting non-default branches
  • Fixed issue where Gitar incorrectly dismissed findings without user request

​
January 8, 2026

​
Mention Gitar with @gitar-bot (Github Only)

On github you can now mention Gitar in your PR comments using @gitar-bot. This works anywhere in your comment and is case-insensitive, making it more natural to ask Gitar questions or make requests without needing to start your comment with “Gitar”.

​
Smarter Inline Comments

Inline code review comments now focus on what matters most - only critical and important findings appear as inline comments on your code. Suggestions and minor issues stay in the main dashboard comment, keeping your PR timeline clean and focused on high-priority items.

​
Recent Activity in Insights Dashboard

The Insights dashboard now shows recent PR activity with detailed metrics for each pull request. View code review findings, rules applied, and CI analysis at a glance, with expandable cards for deeper investigation.

​
Usability Improvements

  • Linear issue references in comments are now automatically converted to clickable hyperlinks

​
Bug Fixes

  • Fixed a bug where Gitar’s code review agent incorrectly treated 2026 as a future year
  • Fixed insights chart showing gaps when dates have no data in the selected time range
  • Fixed bot allowlist behavior to correctly skip bot PRs when the allowed bots list is empty
  • Code review does not report stylistic issues related to spacing and indentation

​
January 6, 2026

​
Inline Code Review Comments

Code review findings now appear as inline comments directly on the relevant lines of code in your pull requests. This enhancement makes it easier to understand and address feedback in context, with precise file and line locations for each finding. Key improvements:
  • Inline comments show the verdict at the top with detailed findings collapsed by default in a “Details” section
  • Automatically resolves inline review comments when the associated finding is addressed in subsequent commits
  • New organization setting to control inline comments mode (enabled by default for new organizations)

​
Natural Conversation with Gitar

Reply to Gitar’s comments naturally without typing “gitar” at the start. Gitar now detects when you’re replying to its comments, enabling more conversational interactions.

​
Code Review and Rules Insights

The Insights dashboard now shows statistics for Code Review and Repository Rules activity. New summary cards display PRs processed, code review issues, CI failures, and comments addressed with daily averages, plus an activity trends chart with date range filtering. Code Review Findings - Breakdown by category (Security, Bug, Performance, Edge Case, Quality) with severity levels and resolution tracking. Top Rules Applied - See your most triggered rules with compliance percentages and action counts.

​
Usability Improvements

  • The “Run Now” button for generating CI failure reports is now available in all states of the Insights dashboard, including when viewing empty states or errors.
  • Code review now considers PR/MR title and description for better context-aware feedback
  • Findings are preserved across reviews
  • PR-level code review toggle removed - The gitar code-review:on/off commands have been removed from the dashboard comment. Code review is now controlled exclusively through organization settings.

​
Bug Fixes

  • Fixed missing skeleton loader for Top Failures section during page refresh in Insights dashboard Fixed a bug that prevented Jira integrations from being uninstalled
  • Improved dashboard loading performance with optimized font loading and skeleton states

​
December 23, 2025

​
Proactive CI Failure Detection for Auto-Apply

When you enable the “Auto-apply” setting on a PR/MR that already has failing checks, Gitar now proactively analyzes and acts on those failures immediately instead of waiting for new activity.

​
Bot PR Filtering Controls

Configure which bot accounts Gitar should process through a new “Allowed Bots” setting in organization configuration. By default, all bot changes (like dependabot) are skipped unless explicitly allowlisted.

​
Onboarding Flow Improvements

  • Allows users to invite their code hosting platform administrator from the Connect Code page in the onboarding flow.
  • Breaks up the post-code-connection onboarding flow into multiple steps for a more guided onboarding experience - CI Setup, Workflow Setup, and Integration Workflow Setup.

​
Bug Fixes

  • Fixes a bug where inline comments to Gitar were not receiving an eyes reaction when processed.

​
December 15, 2025

​
On-Demand CI Failure Reports

Generate failure analysis reports instantly with the new “Run Now” button in the Insights dashboard. Previously available only on a scheduled basis, you can now trigger reports on demand to analyze your CI failures across the last 7 days whenever you need them.

​
Improved Code Review Display

Code review comments now feature a cleaner, more scannable format that highlights what matters most. The new design includes verdict badges such as Approved and Changes requested at the top, uses emoji prefixes instead of section headers, and automatically expands when critical or important issues are detected. Less important details like suggestions and resolved findings are tucked into a collapsible “More details” section to keep the focus on action items.

​
Bug Fixes

  • Fixed an issue where the Insights dashboard platform picker would default to GitHub even when only GitLab repositories were connected
  • Resolved a bug in settings page navigation that could cause incorrect redirects before feature flags finished loading
  • Code review now only includes “What Works Well” section for substantial changes, avoiding unnecessary positive highlights on trivial updates like dependency version bumps

​
December 12, 2025

​
Jira Integration

Connect your Jira workspace to Gitar and automatically keep issues and pull requests in sync. The integration supports OAuth 2.0 or Personal Access Token authentication and enables workflow automation through repository rules. Jira Five new built-in rules are available in the catalog:
  • Jira Auto-Linking: Find and attach relevant Jira issues to changes without linked tickets
  • Merge Close Jira Comment: Add implementation summary to linked Jira issues when changes are merged
  • Multi-Issue Relationship Linking: Link related Jira issues when multiple are attached to a single change
  • Reviewer Assignment from Issue: Auto-assign reviewers based on Jira issue watchers and stakeholders
  • Unaddressed Items Follow-up: Create Jira issues for unresolved comments and TODOs when changes merge

​
Code Review

Gitar now automatically reviews your pull requests and merge requests, providing AI-powered feedback on code quality, edge cases, and potential issues. Reviews appear directly in your dashboard comment with findings organized by severity into Important, Suggestions, and Resolved sections. Each review also highlights what works well and provides actionable recommendations. Code Review Enable at Organization Level: Toggle automatic code review in your organization settings. When enabled, Gitar will review code changes on all PRs/MRs, providing feedback and suggestions. Custom Review Instructions: Add markdown files to .gitar/review/ in your repository to customize the review process with project-specific guidelines, coding conventions, and gotchas that Gitar should watch for.

​
GitHub Status Check Visibility Settings

Control whether Gitar shows a status check indicator on your GitHub PRs while processing. Disable this setting to reduce visual noise in the GitHub Checks tab if you find it confusing alongside other CI checks.

​
Redesigned Dashboard Comment

The dashboard comment has been completely redesigned with a cleaner, more compact layout. Code Review, Rules, and Options are now collapsible sections that show status at a glance. Collapsed view shows key status indicators inline: Expanded Options reveals a clean table layout with all available commands and copy buttons for easy use:

​
Audit Logs for Configuration Changes

Configuration changes to organization, repository, and agent settings are now tracked in audit logs with user attribution and timestamps. This provides full visibility into who made changes and when, improving security and debugging capabilities.

​
Usability Improvements

  • Integration rules can now navigate directly to OAuth flows from the rules catalog
  • Active settings page is now highlighted in the navigation sidebar for better orientation
  • Dashboard handles empty states more gracefully with helpful messages

​
Bug Fixes

  • Fixed GitHub sign-in button styling issues
  • Improved handling of configuration overwrites for code review settings

​
December 9, 2025

​
Introducing Commands

You can now control Gitar’s behavior using commands - special phrases you comment on your PR/MR. Unlike regular comments to the Gitar agent, commands must match exactly (case insensitive) and take effect immediately. Commands & Interactions Auto-Apply - Control whether Gitar automatically commits updates to your branch:
  • gitar auto-apply:on - Enable automatic updates
  • gitar auto-apply:off - Disable automatic updates (suggestions only)
The dashboard comment displays the current auto-apply status. This fixes a long-standing issue where developer roles on GitLab could not control the auto-apply behavior. Display Mode - Control how much detail you see in the dashboard comment:
  • gitar display:verbose - Show all rules including those that don’t apply, with explanations
  • gitar display:compact - Show only relevant rules (default)
Your preference persists across comment updates, and the footer shows a hint for the opposite command. Compact mode (default) shows only applicable rules with a summary of hidden rules: Verbose mode shows all rules with explanations for why each doesn’t apply:

​
Reduced Comment Noise

Dashboard comments now generate even fewer email notifications. Comments only repost when you push new commits. In all other cases, the comment is updated in place.

​
Bug Fixes

  • Fixed an issue where rules would report taking actions (like suggesting comments or correcting typos) without actually performing them

​
December 4, 2025

​
Slack Integration

Connect your Slack workspace to Gitar to enable automated notifications and workflow actions. Send messages and fetch information from channels and groups-all triggered by repository rules. For example, alert an on-call engineer when infrastructure CI failures are detected, or use context from the latest Slack thread to fix an issue. Slack

​
New Linear Rules in Catalog

Five new built-in rules are now available for Linear integration:
  • Linear Auto-Linking: Automatically find and attach relevant Linear issues to PRs/MRs that don’t have linked tickets
  • Summary of change to Linear issue: Add implementation summaries to linked Linear issues when changes are merged
  • Multi-Issue Relationship Linking: Create relationships between multiple Linear issues attached to the same PR/MR
  • Reviewer Assignment from Issue: Auto-assign reviewers based on Linear issue watchers and stakeholders
  • Unaddressed Items Follow-up: Create follow-up Linear issues for unresolved review comments and new TODOs when changes merge

​
Improved Onboarding Experience

New users now experience a simplified onboarding process after signing up. The flow guides users through organization setup, code connection, and CI and Rules configuration with clearer steps and better error handling. New users also receive a welcome email upon signing up to help them get started quickly.

​
Reduced Email Noise from GitHub/GitLab

Significantly reduced the number of email notifications triggered by Gitar’s dashboard comment updates. The dashboard comment now only moves to the bottom of the PR/MR timeline when new commits are pushed. Previously, the comment would move on every status update, generating unnecessary notification emails.

​
Usability Improvements

  • Organization switcher is now visible for all users, making it easier to manage organization settings and customize your workspace
  • CI success events now automatically hide stale failure analysis to keep your PR timeline clean
  • GitLab subgroups are now searchable when configuring repositories
  • Dashboard comment now shows a spinner in sync with the GitHub check run status for consistent visual feedback

​
Bug Fixes

  • Fixed issue where GitLab dashboard comments were not being reposted correctly
  • Improved handling of PRs that are merged while Gitar is still processing
  • Resolved duplicate code review comment issues
  • Fixed issue where your “auto-accept changes” checkbox preference was reset when the dashboard comment updated

​
November 26, 2025

​
Single Dashboard Comment

Gitar now creates a single dashboard comment for all PRs/MRs that updates with the latest status, including failure analysis and rule evaluation. It also moves later in the timeline so you do not lose track of it. It features cleaner visual organization with reduced clutter keeping the most important information at the top.

​
Linear Integration

You can now connect your Linear workspace to Gitar and automatically create context/run rules to automate Linear issue updates.

​
Request Changes on PRs

Gitar can now block PR merges by requesting changes when critical issues are detected during automated analysis or rule evaluation, providing stronger enforcement of quality gates and compliance requirements.

​
Rule Evaluation on PR Close

Repository rules now evaluate when PRs are closed or merged, enabling post-merge workflows like compliance reporting, documentation generation, and notification triggers based on the final state of merged changes.

​
Usability Improvements

  • Added ability to copy text from reports for easier sharing and documentation

​
Bug Fixes

  • Improved rule analysis to assess final state after all actions complete
  • Fixed some reliability issues with long running agent runs

​
November 18, 2025

​
Native Bitrise Integration

Bitrise support has been added as a native built-in integration alongside CircleCI and Buildkite. Connect your Bitrise workspace to enable CI failure analysis, log fetching, and automatic retry operations directly from Gitar.

​
Structured PR Summary Format

The PR Summary Enhancement rule now generates more organized, scannable summaries with hierarchical formatting. Summaries prioritize high-impact changes like new files, APIs, and features over implementation details, using bold categories and code formatting for technical terms.

​
Enhanced Rules Evaluation Display

Repository rules evaluation results now show detailed requirement and action status tracking. Each rule displays whether its requirements were met and what actions were taken, providing better transparency into automated workflows. Files with multiple rules are now grouped together into sub-sections.

​
Refreshed Configuration Interface

The organization settings configuration page has been redesigned with improved organization and clearer sections for agent configuration, monitoring settings, and repository management. Settings are now easier to find and configure.

​
Compact Analysis Comments

CI failure analysis comments now use a more compact, scannable format. The summary line is clickable to expand full details, and feedback prompts are integrated inline using smaller text. This reduces visual clutter while keeping all information accessible.

​
Performance and Usability Improvements

  • Integrations are now in their dedicated settings page
  • Improved latency of building context upon PR/MR creation
  • Improved failure analysis tone to focus on recommended fixes rather than applied changes

​
Bug Fixes

  • Improved reliability of Gitlab webhook delivery
  • Fixed issues with reading large image screenshots attached to PRs/MRs

​
November 10, 2025

​
Built-in Rules from Catalog

Access a curated library of pre-built repository rules without writing custom configurations. Enable rules like PR Summary Enhancement, Log Consistency, Flaky Test Retry, and more directly from your settings.

​
Context-Aware Rule Evaluation

Rules now consider previous evaluation results when analyzing new changes, enabling smarter decision-making across multiple PR/MR updates. This provides more consistent and accurate automated actions ensuring rules can track progress and make informed decisions based on historical context.

​
Native CircleCI and Buildkite Integration

CircleCI and Buildkite support has been upgraded from MCP server integration to native built-in tooling. This provides reliable CI operations including log fetching, status checking, and job retrying.

​
Analysis Feedback Collection

Help improve Gitar by providing feedback on CI failure analyses. You can react to analysis comments with thumbs up/down to indicate helpfulness. Your feedback helps the system to provide better analysis over time.

​
Enhanced Analysis Reports with Attribution

Analysis reports in the Insights dashboard now include improved formatting with proper attribution of failure causes. The Top Failures section displays more detailed breakdowns and clearer categorization of build, test, and infrastructure failures.

​
November 5, 2025

​
Top Failures in Insights Dashboard

The Insights dashboard now displays a breakdown of your most common CI failures, categorized by type (Build, Test, Flaky Test, Configuration, Tooling, Infrastructure). Each category shows specific failure patterns like “Incorrect test assertion - wrong expected value” or “CI meta-job cascade failures,” helping teams quickly identify and address recurring issues across their repositories.

​
Enhanced Username Filtering

Fixed a critical issue in the gradual rollout feature where PRs from allowlisted users weren’t being processed correctly.

​
Clearer Dashboard Comment Messaging

Updated the dashboard comment to more clearly communicate when Gitar will push commits to your branch, providing better transparency about automated actions and helping developers understand exactly when to expect changes.

​
Bug Fixes

  • Fixed rules evaluation updates for GitLab repositories where project IDs were incorrectly set to 0, preventing dashboard comments from updating properly
  • Improved emoji display logic in rules evaluation results for more consistent and clearer visual feedback
  • Fixed onboarding flow for users with organizations who haven’t yet installed the GitHub app
  • Resolved issue where push operations were attempted during analysis-only runs

​
October 22, 2025

​
Repository Rules Evaluation Transparency

Rules evaluation results are now displayed directly in the dashboard comment, showing which rules were triggered and what actions Gitar took. This provides full transparency into automated workflows and helps teams understand Gitar’s decision-making process.

​
Improved Comment Structure

Enhanced comment formatting with better organization and reduced verbosity. Analysis comments now include commit links in the title and use a more structured template for easier scanning.

​
More Events for Rules Evaluation

Gitar can now listen to and evaluate rules on PR/MR metadata updates, including Title, Description, and Labels. Build failure analysis comments now reference the commits they are referring to with a link.

​
Bug Fixes

  • Fixed rebase handling when users force push to branches
  • Resolved issues with PR number extraction in various workflows
  • Better handling of duplicate comments
  • Fixed a bug where build failure analyses were missing from some Gitar comments
  • Improved the structure of build failure analyses in comments

​
October 8, 2025

​
Gradual Rollout Options

Admins can now control which developers’ PRs/MRs Gitar processes by configuring a list of allowed GitHub/GitLab usernames. This enables gradual rollout to specific teams or users before enabling organization-wide, perfect for testing and phased deployments. Scope settings

​
Cleaner Comments

CI failure analysis now shows a short summary and details are now collapsed by default in notification comments. This reduces comment spam, while keeping detailed information accessible when needed. Gitar will now post failure analysis comments for each push. Each comment displays the current status of the auto-fixer and provides a link to the dashboard comment where you can enable or disable automatic fixes.

​
Fixed Pre-commit Hook Issue

Fixed a bug preventing fixes for environments with pre-commit hooks configured.

​
Fixed Unintentional Push Issue

Resolved an issue where Gitar attempted git pushes during runs where only failure analysis was done. The agent now correctly skips push operations when no code changes are required.

​
October 6, 2025

​
Inline Comments

Gitar will now make inline comments on your MRs in GitLab when appropriate.

​
Enhanced Insights Metrics

Insights now separately track CI failures analyzed and PRs/MRs processed for more accurate visibility into Gitar’s activity and improved cost savings calculations.

​
October 2, 2025

​
CI Failure Analysis

Gitar now automatically analyzes CI failures and provides insights directly in the dashboard comment, helping you understand what went wrong before attempting a fix. Analysis results update dynamically as new commits are pushed. Learn more about CI failure analysis & fixes

​
Repository Rules

Gitar can now interpret repository rules written in natural language and automatically execute actions. Rules are defined as md files in .gitar/rules folder in your repository. This can be used to execute workflows. Here is an example md file you can add at .gitar/rules/package_upgrades.md
Learn more about repository rules

​
Improved Dashboard Comment Structure

  • Changed the CI fix checkbox from “Do not fix CI failures” (checked by default) to “Fix CI failures” (unchecked by default) for clearer intent.
  • Gitar now clearly communicates that it never force pushes to your branch.

​
Enhanced Dashboard Filtering

The dashboard page now only shows runs with actual build failure analysis and fix attempts, filtering out context-gathering runs to provide a clearer view of Gitar’s work on your PRs.

​
September 23, 2025

​
Gitar is Commit Aware

Gitar no longer force pushes changes. This prevents the agent from overwriting your changes while it works. With this new feature the PR/MR is no longer frozen and developers can work alongside Gitar. Gitar will rebase its changes on the most recent pushed changes automatically, enabling collaboration without conflicts.

​
One Click Installs

Install the GitHub app and start using Gitar. No account needed.

​
Status Comment Resources

Status comments now include helpful documentation and support links in the footer.

​
September 19, 2025

​
Enhanced Organization Setting Handling

Gitar now properly handles in-flight merge requests that receive activity after the organization’s “Automatically fix CI failures” setting is enabled, ensuring consistent behavior across all active MRs.

​
Improved Comment Volume Handling

Fixed an issue where developer preference for [ ] Do not fix CI failures on high-activity comment conversations (exceeding 20 comments) were not being respected consistently.

​
September 15, 2025

​
Recent Activity

The app now displays Recent activity below the insights.

​
GitLab Nested Groups Support

GitLab merge requests with nested groups (like group/subgroup/project) are now properly parsed and processed.

​
Improved Run Cancellation Logic

Fixed edge cases in automatic run cancellation when new commits are pushed, ensuring proper cleanup of in-progress CI-related tasks while preserving other pending work.

​
September 12, 2025

​
Status Updates via Gitar Check Run in GitHub

Status updates are now live, showing real-time progress when Gitar is processing your PRs.

​
Enhanced CI Configuration for Team Plans

CircleCI and Buildkite configuration options are now available for Team Plans.

​
Smart PR Description Processing

If your PR description starts with “Gitar”, we now automatically act on it.

​
Automatic Cancellation on PR Updates

Gitar now listens to GitHub push events. If there is a run in progress for a PR and you push new commits, we cancel the old run, incorporate your latest changes, and rerun against the updated CI results to keep fixes aligned with your most recent code.