Ask about pull requests where your team already talks
Mention @MergeHarbor in a Slack, Microsoft Teams or Google Chat thread to ask about a pull request, summarise its review, explain a finding, or open a fix pull request behind a confirm button.
Review of acme/payments#212 · confidence 4/5
1 · major · pay/refund.go:42 · a refund can exceed the charge 2 · minor · pay/ledger.go:88 · the ledger write is not retried
Answered from the stored review · no credits used
How it works
Install the app
Add to Slack in one click from the console. For Teams and Google Chat, add the app to a team or space, then confirm the connection in the console.
Map channels to repositories
Give each channel a set of repositories, a role (ask, fix or approver) and optional monthly credit caps. The most specific mapping wins.
Ask in a thread
Paste a pull request link, then ask a question, write summarise, explain finding 2, status or open a fix. Follow-ups in the thread need no link.
What you get
- Only questions use credits
- Summaries, finding explanations and status come from the stored review and use no credits. A question asked before is answered from cache.
- Fixes need a confirm
- A fix pull request opens only when the author or an approver presses the button, depending on the channel's role. Every confirmation is audited.
- Private repositories stay private
- A public channel is never answered about a private repository unless that channel is mapped to it by name. Code snippets are withheld in public channels by default.
- People linked to members
- Chat users are linked to MergeHarbor members by email address, or with a one-time link. People who are not linked get read-only answers.
- Alerts with buttons
- Review alerts go to a channel, to every channel mapped to the repository, or to the author's direct messages, with Explain, Open fix PR and Mute 24h buttons.
- An activity log
- Every request with its channel, outcome, credits and cost, filterable and exportable as CSV. Message text is not stored in the log.
Frequently asked questions
How do Teams and Google Chat differ from Slack?
They do the same things. Teams has no ephemeral messages, so refusals are posted in the thread. Neither has a slash command, and neither reads earlier channel messages: follow-ups use MergeHarbor's own redacted thread memory.
Is there a Discord app?
Yes. In Discord you use the /mergeharbor slash command instead of mentions, so MergeHarbor never sees other messages in your server. It works in server channels, not direct messages.
What does MergeHarbor store from chat?
Per thread, only which pull request it is about and a short redacted summary. Questions and answers are kept on the pull request like questions in the console. The activity log keeps no message text.
Do we still need webhooks for alerts?
No, but you can keep them. Incoming webhooks to Slack, Microsoft Teams and Google Chat remain the simple option when you only want alerts, with nothing to install.
Have another question? Ask our support team
Review every pull request with the context of your whole codebase
Connect a code host in minutes. Reviews start right away, and codebase context is added as indexing completes.