Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.gitar.ai/llms.txt

Use this file to discover all available pages before exploring further.

Gitar works directly in your PR/MR interface. All interactions, status updates, and approvals happen right where you code — no context switching to external dashboards.

​
Dashboard Comment

When a new PR/MR is created, Gitar posts a comment used for status updates and controls. Gitar posts status updates about its activity by updating this comment in realtime. You can control default behavior like enabling automatic CI failure fixing etc.

​
CI Failure Analysis & Fixes

When CI fails, Gitar automatically analyzes the failure and posts a comment explaining why. The analysis identifies root causes and provides context before attempting any fixes. You can review the analysis to understand what went wrong, then:
  • Enable auto-apply on the PR with gitar auto-apply:on so Gitar pushes a fix commit automatically
  • Push your own fix with the context from the analysis
  • Comment Gitar <specific instruction> for a targeted fix
Gitar is capable of fixing build errors, linting errors, test failures, and more. The analysis updates dynamically as new commits are pushed.

​
Address Review Comments

Ways to address Gitar in PR/MR comments:
  • Start the comment with Gitar (case-insensitive)
  • Use @gitar as a prefix — e.g. @gitar fix this bug
  • On GitHub, mention @gitar-bot anywhere in the comment
  • Reply directly to one of Gitar’s comments — no prefix needed
  • On GitLab, reply to an inline finding — no prefix needed
Gitar only processes comments from users with repository write access for security reasons. Be specific and actionable in your requests. Gitar reacts to your comment with an eyes emoji to indicate it has started working on it.

​
Example

Here is an example of Gitar fixing CI failures and addressing user comments on a PR. After the initial message, a user posts a request via a comment. Gitar acknowledges it is looking at the request. CI has also failed because of test failures. After a few minutes, Gitar resolves both issues and pushes commits to the PR and explains what it did. At this point, the user comment as well as CI failures are solved. CI is green and the PR is ready for merging.

​
Troubleshooting

If Gitar isn’t responding to your comments, verify:
  • Your comment addresses Gitar — start with Gitar (case-insensitive), @gitar, or @gitar-bot (GitHub). Replies to one of Gitar’s own comments work without a prefix.
  • You have write access to the repository (only users with write access can trigger Gitar responses)
  • If you want Gitar to push a fix automatically, auto-apply is enabled on the PR — toggle it with gitar auto-apply:on
If CI continues to fail after Gitar’s attempts:
  • Multiple iterations may be needed — complex CI failures sometimes require several rounds of fixes
  • Gitar will automatically iterate on new CI failures to resolve them and make CI green
  • Provide additional context by commenting with more details about the specific failure
  • Gitar maintains full context of your PR/MR throughout its lifetime, so you can comment to steer behavior at any time
  • Consider configuring repository instructions on how to best use your build environments and development practices by giving it custom AI rules