Overview
Gitar monitors your CI pipelines and automatically analyzes failures on every PR. It identifies root causes, posts detailed breakdowns, and can push fixes.Which CI Platforms Need Connecting
Gitar reads CI logs so review and repair can follow the pipelines attached to the repository. Gitar reads GitHub Actions, GitLab Pipelines, Bitbucket Pipelines, and Azure DevOps Pipelines with no setup, using the credential from your code host connection. The AWS CodeCommit preview also supports CodeBuild and CodePipeline analysis when CI access is granted during setup. Every other CI platform reports its builds to the pull request as a status check, and Gitar needs its own credential to follow that link and fetch the log. Connect the ones in use:How It Works
When CI fails on a PR, Gitar automatically:1
Analyze the failure
Gitar reads the CI logs, identifies the failing step, and determines the root cause of the failure.
2
Post an analysis comment
A detailed explanation of the failure is posted to the dashboard comment on your PR, including which files and lines are involved.
3
Suggest or apply a fix
With auto-apply on, Gitar can push fixes for failures confirmed as caused by the PR. With auto-apply off, you can request a fix explicitly. Recovery after a Gitar fix can also push a follow-up repair when its conditions are met.
Applying Fixes
After Gitar posts its analysis, you have three options:
With auto-apply on, Gitar automatically fixes only failures its analysis confirms were caused by the PR. It skips automatic fixes when the cause is unrelated or uncertain. You can still request a fix explicitly with
Gitar fix CI.
Auto-apply can be toggled at any time with gitar auto-apply:on / gitar auto-apply:off. See Commands & Interactions for all available commands.
CI Retry for Unrelated Failures
Gitar can automatically retry CI jobs associated with unrelated failures, such as flaky tests or transient infrastructure failures. Related or uncertain findings do not trigger retries. Turn on Retry unrelated CI failures under Settings -> Configuration -> Behavior, independent from auto-apply. Retry works on GitHub Actions, GitLab Pipelines, Bitbucket Pipelines, Azure DevOps Pipelines, and CircleCI. CircleCI reruns the whole workflow. Gitar avoids repeatedly retrying the same failed run. On Bitbucket, a retry creates a new pipeline, and Gitar does not automatically retry that pipeline again. On GitLab, Gitar checks the job’s attempt history within the same pipeline before retrying it. If the job has already been retried, or Gitar cannot verify its identity or attempt history, Gitar skips the automatic retry. In the AWS CodeCommit preview, Gitar retries standalone CodeBuild builds. For CodePipeline, it retries a stage only when every failed action is unrelated to the PR. Other connected CI platforms get failure analysis without retry. On Azure DevOps Cloud and Server, the PAT needs Build (Read & execute) for retries. Build (Read) is enough for analysis. See the Cloud or Server setup guide.Recovery after a Gitar fix
When Gitar breaks previously passing CI, it can attempt a follow-up repair with auto-apply off. Recovery requires the latest failure to be related to the PR, with one or two consecutive Gitar commits after a commit whose CI passed. This recovery is separate from retrying an unrelated flaky job. See CI Retry for Unrelated Failures for that setting.Multi-Iteration Fixing
CI failures may not be resolved in a single pass. Gitar supports multi-iteration fixing:- Gitar pushes a fix for the original CI failure.
- CI re-runs on the updated branch.
- If CI fails again (whether from the same issue or one the fix introduced), Gitar re-analyzes the new failure.
- Gitar attempts another fix, taking into account the full history of previous attempts.
Gitar to request another fix: