Feature support
● supported · ◐ supported with a difference, see the note · ○ not available
1 See Code Review for how each host applies a fix.
2 Reply
gitar fix on the finding instead. Same result, one more comment.
3 Only where the instance enforces merge-request approval rules; elsewhere Gitar places no gate and posts no blocking comment. See Block Merge.
4 Bitbucket records the review and shows it, and does not treat it as a merge gate. A person can still merge.
5 Bitbucket Cloud has no native auto-merge to arm.
6 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.
7 GitLab merges using the project’s own merge-method setting.
8 Data Center reports build status on a poll rather than a push, so analysis starts a little later than on the other hosts.
9 The commit is signed and verifies locally, with no badge on the platform. See Signed Commits.
10 Gitar registers its key when you connect. See Signed Commits.
Self-hosted and server editions
A self-hosted server has to be reachable from Gitar and able to send webhooks out. See Network Access.