mergeme.dev valid
MergeMe
MergeMe delivers GitHub pull request and GitLab merge request notifications to Slack for code review. Each PR/MR gets one updating Slack card - status changes update the existing message in place instead of posting a new notification per event. Comments are posted as thread replies on that card.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://mergeme.dev/llms.txt
- llms-full.txt
- https://mergeme.dev/llms-full.txt
- Sections
- 10
- Links
- 24
- Size
- 5667 bytes
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T09:56:30.180Z
- Last checked
- 2026-10-27T09:56:30.913Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:56:30.339Z. Cached copy · Source on mergeme.dev
# MergeMe
> MergeMe delivers GitHub pull request and GitLab merge request notifications to Slack for code review. Each PR/MR gets one updating Slack card - status changes update the existing message in place instead of posting a new notification per event. Comments are posted as thread replies on that card.
It supports GitLab.com (OAuth), GitLab self-hosted (manual webhook), and GitHub.com (GitHub App).
One workspace can connect multiple git sources; Slack remains one connection per workspace.
## Key features
- Single updating Slack card per PR/MR - status changes update the existing message in place
- Optional CI checks/pipeline rollup on each card (e.g. CI: Running (2/5)) - enable in Routing > Preferences
- Configurable sidebar colour per PR/MR status on the Slack card - Routing > Preferences
- GitLab/GitHub @mentions in comments resolved to Slack @mentions via user mappings
- Per-workspace channel routing - different projects can post to different Slack channels
- Multi-git per workspace: GitHub + GitLab.com + self-hosted in one place
- Per-mapping git source; grouped project/user pickers in routing
- Scheduled Slack digests of stale open PRs/MRs (GitHub and GitLab.com; Routing > Reminders)
## Providers
| Provider | Setup | Webhook registration |
|---|---|---|
| GitLab.com | OAuth - automatic | MergeMe registers webhooks via GitLab API |
| GitLab Self-Hosted | Manual - paste webhook URL into GitLab | You add the webhook to each project |
| GitHub.com | GitHub App install - automatic | GitHub App handles it globally |
## Setup overview
### GitLab.com (~5 minutes)
1. Sign in at mergeme.dev, create a workspace, pick GitLab.com as your main platform
2. Sources → Slack: connect your Slack workspace
3. Sources → GitLab.com: Connect GitLab (OAuth)
4. Routing → Channel mappings: select a project, pick a Slack channel
5. Routing → User mappings (optional): map GitLab usernames to Slack users
### GitLab Self-Hosted (~10 minutes)
1. Sign in at mergeme.dev, create a workspace, pick Self-Hosted GitLab as your main platform
2. Sources → Slack: connect your Slack workspace
3. Sources → Self-hosted: copy webhook URL and signing token (or secret token for GitLab < 19.0)
4. In GitLab: Settings → Webhooks → Add webhook, paste URL and token, enable MR + Note events (and Pipeline events for CI status on cards)
5. Routing → Channel mappings: enter project ID, pick a Slack channel
6. Repeat step 4 for each project
### GitHub.com (~5 minutes)
1. Sign in at mergeme.dev, create a workspace, pick GitHub.com as your main platform
2. Sources → Slack: connect your Slack workspace
3. Sources → GitHub: Install GitHub App, choose org/account and repos
4. Routing → Channel mappings: select a repo, pick a Slack channel
5. Routing → User mappings (optional): map GitHub usernames to Slack users
You can add other git sources later from Sources without creating a new workspace.
## Slack notifications trigger when a PR/MR transitions to
- opened / reopened
- in review (
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| mergify.com | Mergify | interface DevOps and observability Developer tools | FR | 58 | ✓ | ||
| s2p.dev | S2P (Ship 2 Post) | documentation Productivity Marketing | CH | 45 | ✓ | ✓ | |
| hoplite.sh | Hoplite | documentation AI agents and MCP Developer tools | US | 47 | ✓ | ||
| aviator.co | https://aviator.co/ llms.txt | documentation AI and machine learning Developer tools +1 | US | 51 | ✓ | ||
| coderabbit.ai | CodeRabbit | documentation Developer tools AI and machine learning | — | 61 | ✓ | ||
| gitkraken.com | GitKraken | transactional AI and machine learning Developer tools +1 | US | 62 | ✓ | ||
| productlane.com | Productlane | transactional Business software Communications | — | 59 | ✓ | ✓ | |
| korekt.ai | Korekt AI | documentation AI and machine learning Developer tools | US | 46 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=mergeme.dev · GET /v1/domain/mergeme.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage mergeme.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for mergeme.dev:
1. POST https://agentwebmap.com/v1/sites/mergeme.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://mergeme.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/mergeme.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/mergeme.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.