Is this the same as the GitHub app for Slack?

No. The GitHub app for Slack subscribes a channel to repositories you choose — /github subscribe owner/repo — and has no keyword search. FishOut looks for your keywords in issues and pull requests anywhere on public GitHub.

Does it include comments on issues?

Issues and pull requests are what arrive with a title today; a matching comment links to its issue without a title of its own. The sample here is an issue.

Private repositories?

No. FishOut searches public GitHub only.

How often is GitHub checked?

Every hour, on every plan including Free.

Integrations SlackGitHub

GitHub mentions in Slack, beyond your own repos

Every GitHub-to-Slack integration you will find watches repositories you own: new issues, pull requests, pushes. The issues that name your product in someone else’s repository — a migration that broke, a comparison, a request to support you — are invisible to all of them. That is what FishOut searches for.

Start free The Slack guide

GitHub search runs hourly, Free included. Slack alerts are on every plan.

[01] WHAT ARRIVES/ SLACK MESSAGE

A GitHub post, in Slack

An issue in a stranger’s migration tool about your competitor’s webhooks. GitHub has no Reply call, so the headline just says relevant.

#brand-watch

FishOutAPPnow

Relevant mention on GitHub

Migrating from Notchmail: webhook payloads are missing the thread id

Relevance 82 · Competitor · Negative · by rbaptiste

Labels: Has a problem

Open in FishOut·View on GitHub

[02] WHAT GETS FILTERED/ NOISE

What never reaches Slack

2 GitHub matches that go to Filtered instead, each with its reason.

Filtered · GitHub

Pull request · depsGitHub

Bump acmemail-sdk from 3.2.0 to 3.2.1

Filtered · Off-brief

Automated dependency bumps name your package and say nothing.

Issue · awesome-listGitHub

Add 40 more email tools to the list

Filtered · Below threshold

A list entry is a mention; it is not a conversation.

[03] KEYWORDS THAT WORK HERE/ GITHUB

For GitHub, into Slack

More keyword shapes are on monitoring GitHub.

Your package or SDK name, exactly as published

Issues quote import names and error messages, not your marketing name.

A competitor plus “migrate” or “import”

Migration tooling is where people leaving a competitor leave a public trail.

A floor of 70

GitHub issues are specific and usually real, so 70 lets most genuine bug reports and requests through while dropping list entries.

Settings · Notifications

Slack

GitHub → a channel

Healthy

Relevance floor70

Eventsmention.scored

Batch bursts5 min

[04] SET IT UP/ 4 STEPS

Four steps, about five minutes

GitHub into Slack, start to finish.

1
Create a Slack app and turn on Incoming Webhooks
Walkthrough on the Slack guide.
2
Paste it under Settings → Notifications → Slack
Then send a test.
3
Add GitHub keywords under Keywords
Start with: Your package or SDK name, exactly as published.
4
Floor 70, mention.scored
Batching stays on.

A channel for engineering, another for the rest

GitHub alerts are mostly for engineers; send them to an engineering channel with its own webhook rather than #brand-watch. Each Slack webhook is bound to one channel, so that is a second FishOut channel with its own floor.

[05] A BUSY DAY/ DIGEST

When GitHub gets loud

GitHub mentions come in clusters when a release breaks something downstream: five repositories file the same bug in an afternoon. The digest gathers them into one message, which is also the quickest way to notice they are the same bug.

#brand-watch · 5-min digest

FishOutAPP+5m

3 new mentions for AcmeMail