Gitar Logo

Release Notes

Latest product updates

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.

Rules evaluation

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 (example: Title, Description, Labels, etc.).

Build failure analysis comments now reference the commits they are referring to with a link.

Analysis comment commit 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.

User-based monitoring filters

Learn more about filters

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 easily 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 easily enable or disable automatic fixes.

CI failure analysis comment

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.

Gitar CI failure analysis

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 powerful workflows. Here is an example md file you can add at .gitar/rules/package_upgrades.md

# Package Upgrade Documentation

When package upgrades are detected:
- Add comment with link to upgrade documentation template
- Assign technical lead as reviewer
- Add "needs-documentation" label until template is completed

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.
Gitar dashboard comment

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 users' changes while Gitar is working on. 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 seamless collaboration without conflicts.

One Click Installs

Installing the GitHub app and start using. 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

Gitar status

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

Enhanced CI Configuration for Pro Plans

CircleCI and Buildkite configuration options are now available for Pro 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.