Skip to main content
Gitar works directly in your PR interface. Interactions, status updates, and approvals happen where you code, with no context switching to external dashboards.
Use gitar-skip to skip automatic processing for a PR.

Dashboard Comment

When a new PR 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. From the comment you control default behavior, including automatic CI failure fixing and how much detail the comment shows.

Code review and Verification

The dashboard comment’s Code Review section collects findings and their verdict. Verification collects recorded outcomes after Code Review, while Risk Triage labels the impact of the whole PR. Knowledge-backed findings can carry source citations. Functional Validation lists covered objectives and other issue scope in Verification.

CI Failure Analysis

When CI fails, Gitar automatically analyzes the failure, identifies the root cause, and can push a fix. See CI Failure Analysis for details.

Interactive Commands

Comment on a PR to interact with Gitar: request fixes, ask questions, or toggle settings. See Commands & Interactions for the full list. Explicit fix requests work with auto-apply off. To let Gitar apply fixes automatically, enable auto-apply for the PR with gitar auto-apply:on. See Auto-Apply for review-fix criteria.

Troubleshooting

If Gitar isn’t responding to your comments, verify:
  • Your comment addresses Gitar. Start with Gitar or @gitar (case-insensitive), or mention @gitar-bot anywhere on GitHub. On GitLab, you can also mention the connected GitLab account. Replies to one of Gitar’s comments or inline findings work without a prefix.
  • You have write access to the repository (only users with write access can trigger Gitar responses)
  • The PR’s author and target branch are included in the organization’s processing scope.
  • If the request comes from a bot account, an organization admin has added it to Allowed bots.
  • If Gitar asks you to wait after several requests, wait for the indicated time before commenting again.
If CI continues to fail after Gitar’s attempts:
  • Complex CI failures sometimes need several rounds of fixes
  • Further automatic fixes depend on auto-apply or CI recovery eligibility
  • Provide additional context by commenting with more details about the specific failure
  • Gitar maintains full context of your PR 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