> ## 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.

# Platform Support

> Which Gitar features work on each code host, and what differs

Gitar reviews pull requests on GitHub, GitLab, Azure DevOps, and Bitbucket. Code review, rules, and CI failure analysis run on every host.

What differs is mostly merge control, plus how a fix is applied and whether the host shows a verified badge. The table below is the full picture.

## Feature support

<Info>
  ● supported  ·  ◐ supported with a difference, see the note  ·  ○ not available
</Info>

|                                  |     GitHub     |     GitLab     |  Azure DevOps  | Bitbucket Cloud | Bitbucket Data Center |
| -------------------------------- | :------------: | :------------: | :------------: | :-------------: | :-------------------: |
| **Review**                       |                |                |                |                 |                       |
| Code review with inline findings |        ●       |        ●       |        ●       |        ●        |           ●           |
| Suggested fixes                  |        ●       |        ●       |        ●       |        ●        |           ●           |
| One-click apply                  | ● <sup>1</sup> | ● <sup>1</sup> | ○ <sup>2</sup> |  ○ <sup>2</sup> |     ○ <sup>2</sup>    |
| Rules                            |        ●       |        ●       |        ●       |        ●        |           ●           |
| PR summaries                     |        ●       |        ●       |        ●       |        ●        |           ●           |
| Cross-repo analysis              |        ●       |        ●       |        ●       |        ●        |           ●           |
| **Merge control**                |                |                |                |                 |                       |
| Block merge                      |        ●       | ◐ <sup>3</sup> |        ●       |  ◐ <sup>4</sup> |     ◐ <sup>4</sup>    |
| Auto-approve                     |        ●       |        ●       |        ●       |        ●        |           ●           |
| Auto-merge                       |        ●       |        ●       |        ●       |  ○ <sup>5</sup> |     ◐ <sup>6</sup>    |
| Choose the merge method          |        ●       | ○ <sup>7</sup> |        ●       |        ○        |           ○           |
| **CI**                           |                |                |                |                 |                       |
| CI failure analysis, no setup    |        ●       |        ●       |        ●       |        ●        |     ◐ <sup>8</sup>    |
| Connected CI providers           |        ●       |        ●       |        ●       |        ●        |           ●           |
| **Commits**                      |                |                |                |                 |                       |
| Signed fix commits               |        ●       |        ●       |        ●       |        ●        |           ●           |
| Verified badge on the commit     |        ●       |        ●       | ○ <sup>9</sup> |  ○ <sup>9</sup> |    ● <sup>10</sup>    |

<sup>1</sup> See [Code Review](/features/code-review#providing-feedback) for how each host applies a fix.

<sup>2</sup> Reply `gitar fix` on the finding instead. Same result, one more comment.

<sup>3</sup> Only where the instance enforces merge-request approval rules; elsewhere Gitar places no gate and posts no blocking comment. See [Block Merge](/features/code-review/block-merge).

<sup>4</sup> Bitbucket records the review and shows it, and does not treat it as a merge gate. A person can still merge.

<sup>5</sup> Bitbucket Cloud has no native auto-merge to arm.

<sup>6</sup> Data Center has no "merge when ready" flag. Gitar watches the PR and merges it once Bitbucket's own merge checks pass, so there is no armed state in the Bitbucket UI.

<sup>7</sup> GitLab merges using the project's own merge-method setting.

<sup>8</sup> Data Center reports build status on a poll rather than a push, so analysis starts a little later than on the other hosts.

<sup>9</sup> The commit is signed and verifies locally, with no badge on the platform. See [Signed Commits](/configuration/signed-commits).

<sup>10</sup> Gitar registers its key when you connect. See [Signed Commits](/configuration/signed-commits).

## Self-hosted and server editions

| Deployment                          | Supported                                         |
| ----------------------------------- | ------------------------------------------------- |
| GitLab self-managed, including Free | ● [Guide](/connecting-code/gitlab)                |
| Azure DevOps Server                 | ● [Guide](/connecting-code/azure-devops-server)   |
| Bitbucket Data Center               | ● [Guide](/connecting-code/bitbucket-data-center) |
| GitHub Enterprise Server            | ○                                                 |

A self-hosted server has to be reachable from Gitar and able to send webhooks out. See [Network Access](/connecting-code/network-access).

## Connect a platform

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="/connecting-code/github" />

  <Card title="GitLab" icon="gitlab" href="/connecting-code/gitlab" />

  <Card title="Azure DevOps" icon="microsoft" href="/connecting-code/azure-devops" />

  <Card title="Bitbucket" icon="bitbucket" href="/connecting-code/bitbucket" />
</CardGroup>