Skip to main content
5-minute setup. Free 14-day trial, no credit card required.
By the end of this guide, you’ll have a repository connected to Gitar and see it automatically review a pull request.

​
Prerequisites

  • Access to repositories on GitHub, GitLab, Azure DevOps, or Bitbucket, with permission to connect them to Gitar. See the connection guide for your platform for required permissions.
  • An open pull request, or a repository where you can create one

​
Step 1: Create a Gitar account or sign in

Go to Sign up for Gitar and choose GitHub, GitLab, Microsoft, or Bitbucket. Follow the prompts to sign in with that provider and continue to Gitar. If you already have a Gitar account, select Sign in instead. After signing in to Gitar, continue to repository setup.

​
Step 2: Connect your repository

Select GitHub to add the Gitar GitHub App to your organization. You can grant access to all repositories or select specific ones.
You can change repository access at any time from your GitHub organization settings under Installed GitHub Apps.
After you install the app, your repositories appear under Connected Repositories:
Once your repository appears under Connected Repositories, select Next at the bottom of the page to continue to integrations.

​
Step 3: Optional - Connect integrations

Connect Jira or Linear to give Gitar context from your issues and automate issue management. To skip this step, select Skip and Go to Dashboard at the bottom of the page. You can connect integrations later from settings.

​
Step 4: See Gitar in action

Once connected, Gitar runs an initial scan of your repositories. You have two ways to see it work:
  • Open a new PR. Create a pull request with some changes. Gitar starts working automatically on any PR activity in connected repositories.
  • Try Gitar on existing PRs. In the Gitar dashboard, find the “Try Gitar on Your Open PRs” card and select Start Review beside the pull request you want Gitar to review.

​
Step 5: Review Gitar’s feedback

Open your pull request on GitHub, GitLab, Azure DevOps, or Bitbucket. Within a few minutes, Gitar posts a dashboard comment there with an overview of its analysis. The screenshot below shows Gitar’s dashboard comment on a GitHub pull request. Appearance may vary by platform. Here’s what happens next:
  • CI fails. Gitar analyzes the failure and posts a root cause. If auto-apply is enabled (or you ask for a fix), Gitar pushes a fix commit.
  • Code review. Gitar posts inline review comments on the lines with issues, with a consolidated summary in the dashboard comment.
  • Comment instructions. Reply to Gitar’s comment with natural language to ask for changes.
Gitar never force-pushes to your branch. All fixes are added as new commits so your history stays intact.

​
Next steps

Gitar Dashboard

Learn about dashboard comments, display modes, and auto-apply

Repository Rules

Create automated workflows using natural language

CI Failure Analysis

Deep dive into how Gitar analyzes and fixes CI failures

Connect Your Code

Connect GitHub, GitLab, Bitbucket, Azure DevOps, and other CI providers