Getting Started
Provider Comparison
MergeMe supports three git providers. Here's how they differ in setup, configuration, and behaviour.
| GitLab.com | GitLab Self-Hosted | GitHub.com | |
|---|---|---|---|
| Auth method | OAuth (automatic) | None required | GitHub App install |
| Webhook setup | Automatic via GitLab API | Manual - HTTPS URL in GitLab | Automatic via GitHub App |
| Project listing | Dropdown (from OAuth token) | Manual (enter project ID) | Dropdown (from App install) |
| Terminology | MR / !42 | MR / !42 | PR / #42 |
| Webhook signing | Signing token (HMAC-SHA256) | Signing token (GitLab 19.0+) or secret token fallback | X-Hub-Signature-256 (HMAC-SHA256) |
| Who registers webhooks | MergeMe (automatically) | You (per group or per project) | GitHub App (automatically) |
Which should I choose?
GitLab.com - Your repositories are hosted on gitlab.com. MergeMe connects via OAuth and registers webhooks automatically. This is the easiest setup.
GitLab Self-Hosted - You run your own GitLab instance. Enable self-hosted under Sources > Self-hosted, then paste the HTTPS webhook URL into GitLab - either one group webhook (Premium or Ultimate; recommended) or one webhook per project.
GitHub.com - Your repositories are on github.com. Install the MergeMe GitHub App on your org or account, granting access to selected repos. No per-repo webhook setup is required - the App handles it.