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.

​
General

Gitar is an AI code review and CI fixing agent that works directly in your PR/MR interface. It automatically reviews code changes for security, bugs, and performance issues, analyzes CI failures, and pushes fixes — all without leaving your pull request. See How Gitar Works for a detailed overview.
When a PR/MR is created or updated, Gitar reads the diff, full files touched by the change, CI logs (if CI fails), and any configured repository rules. It then reviews the code, identifies issues, and can push fixes directly to your branch. Findings are posted as inline review comments on the relevant lines; the Gitar dashboard comment on the PR/MR provides a consolidated summary of review, CI analysis, and rule results. See How Gitar Works for the full breakdown.
Gitar is language-agnostic. It works with any programming language or framework. Code review, CI failure analysis, and fix generation all operate on the code as-is, regardless of the language.

​
Security & Privacy

Gitar accesses repositories through secure OAuth integrations with GitHub and GitLab. We only access the specific repositories you configure and only perform the maintenance tasks you approve. All repository access is logged and auditable. See Security for full details.
No. For cloud deployments, code is processed exclusively in ephemeral environments that are destroyed immediately after task completion. We have zero data retention agreements with all our AI providers, ensuring your code is never stored or used for training. Enterprise customers can deploy the agent in their own CI infrastructure, ensuring code never leaves their environment.
No. Gitar does not use customer code for training AI models. Your code remains private and is only used to perform the specific maintenance tasks you request.
Gitar’s processing environments are designed to avoid exposing secrets. Any secrets encountered during processing are not logged, stored, or transmitted outside the secure processing environment. For cloud deployments, the ephemeral architecture ensures secrets exist only in encrypted memory during processing and are erased upon completion. For enterprise CI deployments, secrets remain entirely within your own infrastructure.
Gitar maintains security practices aligned with SOC 2 Type II and ISO 27001 requirements and is fully certified. Regular third-party security assessments are conducted to maintain compliance with industry standards.
Gitar maintains contractual zero data retention agreements with all AI providers including Google and Anthropic. These agreements ensure that no customer code is retained, stored, or used for model training. All processing occurs with zero-retention API endpoints.
Organizations are isolated at the database, application, and infrastructure levels. No organization can access another’s data, configurations, or processing environments.

​
Code Review

Code review can be enabled from your organization settings in the Gitar dashboard. Navigate to your organization settings, find the Code Review section under Features, and enable the toggle. Once enabled, Gitar automatically reviews all new PRs/MRs. See Code Review for details.
Yes. Add markdown files to the .gitar/review/ directory in your repository with custom instructions, checks, or gotchas. Gitar reads these during review to tailor feedback to your project. See Repository Configuration for the full setup.
Reply to the inline review comment to dismiss it — for example, “this is intentional” or “already fixed” — and Gitar processes the reply and drops the finding. On GitHub, resolving the thread also dismisses the finding. Pushing code that addresses the issue resolves the finding automatically: the inline thread is closed and the finding moves to the collapsible “Resolved” section of the dashboard comment. Dismissals persist across review iterations, so Gitar won’t re-raise issues you’ve already closed out.

​
CI Failure Fixing

Gitar handles build errors (compilation failures, missing imports, type errors), test failures (broken assertions, missing setup), linting errors (code style violations, formatting issues), and flaky tests (race conditions, timing issues). See CI Analysis & Fixes for the full list.
If Gitar is unable to resolve a failure after multiple iterations, it posts a summary of what was attempted so you have full context to debug manually. You can also comment with additional context to steer Gitar’s next attempt.
Gitar automatically iterates until CI passes or it determines it cannot make further progress. Each iteration builds on the context of previous attempts to avoid repeating the same fix. There is no fixed limit — Gitar stops when it either succeeds or exhausts productive fix strategies.

​
Billing & Plans

Visit your billing settings at app.gitar.ai and select a plan. Your trial features continue uninterrupted once you subscribe. See Managing Your Subscription for details.
If you don’t upgrade before the 14-day trial ends, automatic processing (code reviews, CI failure analysis, push events) stops. You can still trigger reviews manually by commenting “Gitar review” on any PR/MR. Subscribe at any time to restore full access.
Yes. You can upgrade between Core and Pro at any time from your billing settings. To move to an Enterprise plan, contact support@gitar.ai. Enterprise plans include unlimited seats, custom integrations, and dedicated support.
Contact support@gitar.ai to cancel your subscription. Your access continues until the end of the current billing period.
Your organization and its configuration remain intact. Gitar stops automatic processing but does not delete your data. You can resubscribe at any time to resume service.

​
Integrations

Only one ticket tracker integration can be active per organization. If you need to switch, disconnect the current integration before connecting the other. See Linear or Jira for setup instructions.

​
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
See The Gitar Dashboard and Commands & Interactions for more on interacting with Gitar.
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
  • Provide additional context by commenting with more details about the specific failure
  • Consider configuring repository instructions to help Gitar understand your build environment
See CI Analysis & Fixes for more details.
If Gitar indicates that automatic processing has been paused, your team’s usage is ahead of the included budget pace for the current billing period.
  • You can still trigger reviews manually by commenting “Gitar review” on any PR/MR
  • Automatic processing resumes on its own as the billing period progresses — no action needed
  • Enterprise plans have unlimited usage and are never subject to pace-based limits
See Plans & Billing for more details.
If Gitar posts a message saying you don’t have an assigned seat, it means your organization is on a paid plan (Core or Pro) but an admin hasn’t allocated a seat for your account yet.
  • Ask a team admin to assign you a seat from the organization settings at app.gitar.ai
  • During a trial period, seats are not enforced and all members have full access
See Plans & Billing for more details.