> ## 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 FAQ: AI code review, CI fixes, and data privacy

> Find answers to common questions about Gitar's AI code review, automatic CI fixes, repository access, code privacy, billing, integrations, and troubleshooting.

## General

> [accordion] What is Gitar?
>
> Gitar is an AI code review and CI fixing agent that works directly in your PR interface. It reviews code changes for security, bugs, and performance issues, analyzes CI failures, and pushes fixes without you leaving the pull request. See [How Gitar Works](https://docs.gitar.ai/how-gitar-works.md) for a detailed overview.

> [accordion] How does Gitar work?
>
> When a PR is created or updated, Gitar reads the diff, the 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 carries a consolidated summary of review, CI analysis, and rule results. See [How Gitar Works](https://docs.gitar.ai/how-gitar-works.md) for the full breakdown.

> [accordion] What languages does Gitar support?
>
> 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.

> [accordion] Can I use my own LLM account?
>
> Yes, on Enterprise. Gitar can serve every LLM call from your own Anthropic, AWS Bedrock, or gateway account, and your provider bills you directly. See [Bring Your Own Model](https://docs.gitar.ai/administration/bring-your-own-model.md) and [Plans](https://docs.gitar.ai/account-billing/plans.md).

## Security & Privacy

> [accordion] How does Gitar access my code repositories?
>
> Gitar uses a GitHub App for GitHub and platform-specific credentials for GitLab, Azure DevOps, and Bitbucket. AWS CodeCommit is available in Enterprise preview. Gitar accesses only the repositories you connect. See [Platform Support](https://docs.gitar.ai/connecting-code/platform-support.md) for supported hosts and setup guides.

> [accordion] Is my code stored on Gitar's servers?
>
> Gitar caches repository code on encrypted file volumes to improve performance. Repository caches can persist across processing tasks, and active use can keep cached content available longer. Gitar does not use customer code to train AI models. See [Security](https://docs.gitar.ai/administration/security.md) for data-handling details.

> [accordion] Does Gitar train AI models on my code?
>
> No. Gitar does not use customer code for training AI models. Your code stays private and serves only the maintenance tasks you request.

> [accordion] How does Gitar handle secrets in my code?
>
> Secrets committed to a repository are part of its content and may remain in Gitar's encrypted repository cache until that cached content is removed. They are not limited to the memory or lifetime of a single processing task.

> [accordion] What certifications does Gitar have?
>
> Gitar maintains security controls aligned with SOC 2 Type II and ISO 27001. Third-party assessments run regularly. Contact [security@gitar.ai](mailto:security@gitar.ai) for current attestation status.

> [accordion] What are your zero data retention agreements?
>
> Gitar holds contractual zero data retention agreements with every AI provider it uses. The current providers are on the [Sonar sub-processor list](https://www.sonarsource.com/legal/sub-processors/). Under those agreements no customer code is retained, stored, or used for model training, and processing runs against zero-retention API endpoints.

> [accordion] Does Gitar support SSO?
>
> Yes, on Enterprise. Gitar supports OpenID Connect (OIDC) and SAML 2.0, including setup with Okta. See [SSO](https://docs.gitar.ai/administration/sso.md) for supported protocols and setup requirements.

> [accordion] How does Gitar isolate different organizations?
>
> Organizations are isolated at the database, application, and infrastructure levels. No organization can access another's data, configurations, or processing environments.

## Code Review

> [accordion] How do I enable code review?
>
> Open your organization settings in the Gitar dashboard, find the **Code Review** section under Features, and enable the toggle. Gitar then reviews all new PRs automatically. See [Code Review](https://docs.gitar.ai/features/code-review.md) for details.

> [accordion] Will Gitar change my code automatically?
>
> Auto-apply is off by default. Explicit fix requests can push changes to your branch. CI recovery can also attempt a follow-up repair with auto-apply off when a Gitar change breaks previously passing CI. See [Auto-Apply](https://docs.gitar.ai/features/code-review/auto-apply.md) and [CI recovery](https://docs.gitar.ai/features/ci-failure-analysis.md#recovery-after-a-gitar-fix).

> [accordion] Can I customize what Gitar reviews?
>
> 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 Customization](https://docs.gitar.ai/configuration/repository-config.md) for the full setup.

> [accordion] Does Gitar learn from my feedback?
>
> On Enterprise, Knowledge can learn team conventions from explanations in review comments and apply relevant guidance to later reviews. Dismissing a finding alone does not create a general exception. See [Knowledge](https://docs.gitar.ai/features/knowledge.md).

> [accordion] How do I dismiss a finding?
>
> Reply to the inline review comment to explain why the finding is invalid, or resolve the thread on GitHub to close it without marking it fixed. For accepted concerns and deferred work, see [acknowledging findings](https://docs.gitar.ai/features/code-review.md#providing-feedback).
>
> Pushing code that addresses the issue resolves the finding on its own: the inline thread closes 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 have already closed out.

> [accordion] How do I apply a suggested fix from a review comment?
>
> On GitHub, check the box next to the suggested fix in the inline comment. On GitLab, react with the checkmark emoji. On Azure DevOps and Bitbucket, reply `gitar fix` on the finding. Gitar commits the fix directly to your branch. If a finding has multiple suggested fixes, each one is numbered so you can pick the right one.

> [accordion] Does Gitar amend commits or force-push fixes?
>
> No. Gitar adds fix commits rather than amending existing commits or force-pushing. It handles developer rebases and force-pushes, and your team can squash or fold its fix commits into your preferred history.

> [accordion] What context does Gitar use during code review?
>
> The full repository, not the PR diff alone. Gitar follows imports, checks call sites, and traces how your change connects to the rest of the codebase, which is how it catches broken callers, inconsistent patterns, and missing updates in related files.

> [accordion] Is a high-risk PR the same as a finding?
>
> No. Risk describes the potential impact of the whole change, while findings identify specific issues. Auto-apply addresses eligible findings, not the risk assessment itself. A PR can have no reported defects and still be high risk. See [Risk Triage](https://docs.gitar.ai/features/code-review/risk-triage.md).

> [accordion] Can Gitar check whether a PR meets its ticket requirements?
>
> Yes, on Enterprise. Functional Validation checks objectives from linked issues against the PR diff. An uncovered objective may belong to another change. Objective coverage does not prove runtime behavior or passing tests. See [Functional Validation](https://docs.gitar.ai/features/functional-validation.md) for supported issue sources and linking requirements.

> [accordion] Can Gitar review large PRs and monorepos?
>
> Yes. Gitar supports unlimited changed files per PR, including changes across a monorepo. It selects relevant context and may exclude generated files or other low-value content. Review volume allowances are separate from PR size. See [Large PRs and review volume](https://docs.gitar.ai/features/code-review.md#large-prs-and-review-volume).

> [accordion] Can I evaluate Gitar against historical merged or closed PRs?
>
> Gitar does not have a native back-testing workflow for merged or closed PRs. Evaluating a historical change requires recreating it as a new PR against its original base commit. Contact [support@gitar.ai](mailto:support@gitar.ai) to discuss an evaluation.

> [accordion] How is Gitar different from linters and SAST tools?
>
> Linters and SAST tools match predefined patterns: style violations, known vulnerability signatures, and static rule violations. Gitar reasons about the intent behind your change in context, so it can flag incorrect logic, unhandled edge cases, and drift from the rest of the codebase.
>
> The two are complementary. Run both, and let Gitar cover what pattern matching cannot reach.

> [accordion] Why didn't Gitar review my revert PR?
>
> Gitar skips code review for a PR containing only a single revert commit, even if the original change was never reviewed. Push another commit and code review resumes. CI analysis and rule evaluation still run.

> [accordion] How is Gitar different from GitHub Copilot code review?
>
> Copilot code review works on the PR diff with limited repository context. Gitar explores the full codebase, following imports and checking call sites to reason about how your change affects the rest of the project.
>
> Gitar also pushes fixes directly to your branch, analyzes and fixes CI failures, takes custom review instructions and rules, and re-reviews after every push so findings stay current as the PR evolves.

## CI Failure Analysis

> [accordion] What CI failures can Gitar fix?
>
> Gitar analyzes build errors, test failures, linting errors, and flaky tests. With auto-apply on, it automatically fixes failures confirmed as caused by the PR. Unrelated flaky or infrastructure failures can be retried on supported platforms when retry is enabled. You can also request a fix explicitly with `Gitar fix CI`. See [CI Failure Analysis](https://docs.gitar.ai/features/ci-failure-analysis.md) for supported platforms and recovery behavior.

> [accordion] What if Gitar can't fix the failure?
>
> If Gitar cannot 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.

> [accordion] How many iterations will Gitar try?
>
> Recovery is bounded. The conditions and stopping points are described in [CI Failure Analysis](https://docs.gitar.ai/features/ci-failure-analysis.md#recovery-after-a-gitar-fix). A fresh comment can provide more context when another attempt is needed.

## Billing & Plans

> [accordion] How do I upgrade from the free trial?
>
> Visit your billing settings at [app.gitar.ai](https://app.gitar.ai) and select a plan. Your trial features continue uninterrupted once you subscribe. See [Managing Your Subscription](https://docs.gitar.ai/account-billing/managing-subscription.md) for details.

> [accordion] What happens when my trial ends?
>
> Without an active subscription, the organization returns to the Free plan. Code reviews and PR commands require a plan that includes them. The trial runs 14 days. See [Plans](https://docs.gitar.ai/account-billing/plans.md) for available features.

> [accordion] Can I change my plan later?
>
> 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](mailto:support@gitar.ai)**. Enterprise plans include unlimited seats, custom integrations, and dedicated support.

> [accordion] How do I cancel my subscription?
>
> For Core and Pro, open **Settings → Billing → Manage Billing** and complete the cancellation in Stripe's Billing Portal. Disconnecting a repository does not cancel a subscription or stop billing. See [Canceling a subscription](https://docs.gitar.ai/account-billing/managing-subscription.md#canceling-a-subscription) for the steps and Enterprise support path.

> [accordion] Is Gitar free for open source?
>
> Yes. Vetted open-source projects get Gitar free on the Open Source plan, which includes everything in Pro plus unlimited seats. It covers public repositories on github.com or gitlab.com, and each repo is approved individually. Apply through the [Gitar for OSS application form](https://forms.gle/uESzuYr2Wzs9zm4L7). See [Plans](https://docs.gitar.ai/account-billing/plans.md#open-source-plan) for eligibility and details.

## Integrations

> [accordion] Can I use more than one ticket tracker?
>
> Connect as many ticket trackers as you use. A bare key like `PROJ-123` looks identical across all four, so Gitar attributes it by precedence: Jira first, then Linear, then Plane, then YouTrack. An org running two trackers never resolves a bare key to the second one. See [Jira](https://docs.gitar.ai/integrations/jira.md), [Linear](https://docs.gitar.ai/integrations/linear.md), [Plane](https://docs.gitar.ai/integrations/plane.md), or [YouTrack](https://docs.gitar.ai/integrations/youtrack.md) for setup instructions.

## Troubleshooting

Gitar not responding to your comments, or CI still failing after its fixes? Both are covered in [Troubleshooting](https://docs.gitar.ai/gitar-dashboard.md#troubleshooting). See also [Commands & Interactions](https://docs.gitar.ai/commands.md) for how to address Gitar.

> [accordion] Gitar shows paused automatic processing
>
> The organization has used its automatic-processing headroom for the billing period. On paid plans, reviews on new PRs and comment-triggered work continue, while automatic re-reviews after pushes pause.
>
> Comment **"Gitar review"** to request another review, subject to the plan and seat requirements. Headroom resets with the next billing period and scales with assigned seats.
>
> See [Plans & Billing](https://docs.gitar.ai/account-billing/plans.md) for more details.

> [accordion] Gitar says I don't have a seat
>
> Your organization is on a paid plan (Core or Pro) and no admin has allocated a seat to your account yet.
>
> * Ask a team admin to assign you a seat from Settings → Billing at [app.gitar.ai](https://app.gitar.ai)
> * During a trial period, seats are not enforced and all members have full access
>
> See [Plans & Billing](https://docs.gitar.ai/account-billing/plans.md) for more details.

> [accordion] How do I get help or report a problem?
>
> Contact [support@gitar.ai](mailto:support@gitar.ai) with a description of the problem and the affected PR link, when available. For security questions or vulnerability reports, contact [security@gitar.ai](mailto:security@gitar.ai).

> [accordion] How do I skip Gitar on a specific PR?
>
> Use [`gitar-skip`](https://docs.gitar.ai/labels#gitar-skip) to skip automatic processing for that PR. Explicit comment commands still work.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.