MergeMe logoMergeMe
Published on

GitHub Slack Duplicate Notifications: Find the Sender

Authors
  • Name
    Maruan

To find the cause of GitHub Slack duplicate notifications, first check whether you're looking at a true duplicate at all, then isolate which sender posted each message: the native GitHub app, a second subscription, a GitHub Actions workflow, an incoming webhook or another notification app. A parent message plus a thread reply, or a state change that also appears in the channel, is normal native behaviour and not proof of a second sender.

This runbook is deliberately slow and reversible. You'll record the current setup before touching anything, check for overlapping native subscriptions, look at non-native senders, and only then switch one thing off at a time. It never starts with uninstalling the app or deleting every subscription, because that destroys the evidence you need.

No single cause is assumed here. Several different senders can produce messages that look the same in a busy channel, and the fix depends on which one is actually posting.

Is it really a duplicate? What the native GitHub app posts by design

A message appearing more than once is not automatically a duplicate. The native GitHub app groups related activity into a parent card and its thread. Notifications for each issue or pull request are grouped under a parent message that shows the latest state, with later activity added as thread replies. Some state changes can also be posted to the channel itself, so you may see a thread reply and a channel message about the same change.

Before you suspect a second sender, check three things on the messages you think are duplicated:

  • Is one of them the parent message and the other a thread reply? That is by design.

  • Does the parent message change its status text over time (open, closed, merged)? That is the same message updating, not a new one.

  • Do both messages sit in the channel at the top level with identical content and the same sender name and icon? That is the pattern worth investigating.

The last case is the real signal. Two separate top-level posts for the same pull request or issue event, close together, deserve investigation. They do not by themselves establish which sender or configuration caused them. Note the exact sender label on each (the app name shown beside the message). That one detail often cuts the search in half.

If you only see a parent plus thread, stop here. Nothing is wrong, and muting or removing anything would only reduce visibility.

Record the current setup first: /github subscribe list features and what to note down

Write down the current configuration before changing anything, because every later step is reversible only if you know what to restore. In the affected channel, run /github subscribe list features to see which repositories the channel is subscribed to and which notification features are enabled for each.

Copy the output into a note, along with:

  • The channel name and whether it is public or private.

  • Each subscribed repository or organization, and its enabled features (for example pulls, issues, commits, workflows, reviews, comments).

  • The sender label and timestamp of two example duplicated messages.

  • The repository and event each duplicate refers to (a specific pull request number is ideal).

  • Whether anyone has set up scheduled reminders for that repository or organization.

This record also protects you from scope surprises. Subscription commands apply to the channel, so removing a subscription affects everyone who relies on that channel, not just you. If you keep the original /github subscribe list features output, you can restore any feature later, for example by re-adding pull request notifications with /github subscribe owner/repo pulls.

Don't paste webhook URLs, tokens or workflow secrets into your note or into a shared thread. You only need names and feature lists for this diagnosis.

Check for overlapping native subscriptions: repo, organization, other channels and scheduled reminders

Overlapping native subscriptions are the cheapest thing to rule in or out, so check them before looking at anything custom. Read your recorded /github subscribe list features output and look for these patterns.

Repository and organization both subscribed. The /github subscribe command accepts an organization or a repository. If one channel is subscribed to an organization and also to a repository inside it, the same activity can be reachable through two subscriptions. Compare the two entries and see whether their enabled features overlap.

The same repository in more than one channel. If the duplicate appears across two channels rather than twice in one, check each channel with /github subscribe list features. This is expected if two channels are both subscribed. It's only a problem if you intended one.

Different features covering the same event. Features such as comments, reviews and the default pull request and issue notifications can cover related activity. Check which are enabled on the repository you are chasing.

Scheduled reminders. Reminders are separate from event notifications. A reminder for pending pull request reviews can be delivered by direct message or to a channel, and can be set for yourself, a team or an organization. A reminder that names the same pull request as a live notification can look like a repeat even though it's a different feature. Check the time it posts: reminders arrive on a schedule, not at the moment of an event.

If you find an overlap, resist fixing it yet. Finish the survey of non-native senders first so you change one thing at a time with a full picture.

Check non-native senders: Actions workflows, incoming webhooks and a second notification app

If native subscriptions do not explain the messages, inspect other possible senders next. Look at the sender label on the duplicate you noted earlier. A different name or icon is a strong clue.

GitHub Actions workflows. A workflow with a Slack step posts whenever it runs, entirely independent of your /github subscribe settings. Open the repository's .github/workflows files and search for steps that call Slack, a Slack action or a curl to a webhook. Note which trigger each uses (push, pull_request, workflow_run). A workflow triggered on pull_request that posts to the same channel will sit alongside native pull request notifications. Read the file for structure only, and never copy secrets or webhook URLs out of it.

Workflow notifications from the native app. If both the native workflows feature and a custom Actions step are configured to post for the same run and destination, their messages can overlap. Verify both configurations rather than assuming every run produces duplicates. Your recorded feature list shows whether workflows is on. For a failure-alert pattern, see GitHub Actions Slack Notifications on Workflow Failure.

Incoming webhooks. An incoming webhook added to a channel posts whatever any script sends it. Check the Slack app directory for the workspace and look at which apps and custom integrations are connected to the channel. Native-app webhooks may not appear as ordinary repository-owned hooks, so an empty repository webhook list does not clear the native app. Don't post or share webhook URLs while investigating.

A second notification app. Another GitHub-to-Slack app installed by a teammate, or an older app that was never removed, will post its own copy of the same events. Compare the app name on each duplicate message. Different app names are a useful lead. Confirm their app identities and configurations, since display names and icons alone are not definitive sender identification.

Isolate one sender at a time with reversible steps (and what never to do first)

Isolate by changing exactly one thing, triggering an event, and observing the result before the next change. Use a test pull request or a low-traffic repository so you aren't guessing from live noise.

A workable order, each step reversible:

  1. Pause the most likely non-native sender. If you found an Actions step posting to Slack, agree a temporary change to that notification step with its owner. Keep build, test, deployment and security jobs enabled. A branch-only change affects only runs that use that branch and workflow version, so check the event and branch before drawing conclusions. Trigger a controlled test event and compare messages.

  2. Narrow one native feature. If two native features overlap, remove one with /github unsubscribe owner/repo [feature] and restore it later with /github subscribe owner/repo [feature]. Remember this applies to the whole channel.

  3. Remove one overlapping subscription. If both an organization and a repository inside it are subscribed, unsubscribe the narrower entry only, with /github unsubscribe owner/repo, then confirm with /github subscribe list features.

  4. Test in a scratch channel. Subscribe a new private channel to the repository alone. Invite the GitHub app to the private test channel and subscribe it to the same repository and features. Compare equivalent events, counting parent updates and thread replies separately. A difference narrows the investigation but does not prove the original channel has a second sender.

After each step, run /github subscribe list features again and compare with your saved record so you always know the current state.

What never to do first: don't uninstall the GitHub app from the workspace, don't delete every subscription, don't disable all notifications, and don't remove several senders at once. Each of those hides which sender was responsible, affects colleagues who depend on the channel, and leaves you re-subscribing from memory. For narrowing a single repository, GitHub Slack unsubscribe: Stop alerts for one repository covers the scope of the command in more detail.

After the fix: keeping one clear sender per event, and when a different PR card model is worth a look

Once the duplicate is gone, keep it gone by giving every event type exactly one owner. Write a short note in the channel description or team wiki: native app for pull request and issue events, Actions step only for the deployment result, reminders only in the review channel. When someone adds a new workflow or app, the note tells them where it would collide.

A few habits that prevent a repeat:

  • Re-run /github subscribe list features after any new repository or feature is added to a channel.

  • Prefer one native feature per event type rather than enabling several that overlap.

  • Review connected apps in the workspace periodically and remove abandoned ones.

  • Treat workflow Slack steps as a deliberate choice, not a default, when the native workflows feature already covers the run.

If, after all this, your real frustration is the shape of the notifications rather than a stray sender, a different pull request model may be worth a look. MergeMe shows GitHub pull requests and GitLab merge requests in Slack as one updating card, and supports GitHub.com, GitLab.com and self-hosted GitLab in one Slack workspace. Diagnose overlapping senders first. If you want to compare the presentation across these supported hosts, try MergeMe.

Diagnose the sender first, then decide whether the format needs to change

Compare the sender identity with your recorded /github subscribe list features output, then change one notification route at a time and observe an equivalent test event. Keep one owner per event type, and keep the original setup note so any change can be undone. Keep the change record with the repository and channel configuration so a teammate can restore the intended notifications.

FAQs

Why am I getting the same GitHub notification twice in Slack?

It may be normal native behaviour: the GitHub app posts a parent message with thread replies, and some state changes also appear in the channel. If two identical top-level posts appear, look for overlapping subscriptions, an Actions workflow posting to Slack, an incoming webhook or a second notification app, and isolate one at a time.

How do I unsubscribe from GitHub repo notifications in Slack?

Run /github unsubscribe owner/repo in the channel to remove the repository subscription, or add a feature name to remove just that one. It applies to the whole channel and everyone using it. Record /github subscribe list features first so you can restore it with /github subscribe owner/repo.

How do I see what a Slack channel is subscribed to on GitHub?

Run /github subscribe list features in that channel. It shows the subscribed repositories and which notification features are enabled for each. Save the output before changing anything, since it is your reference for restoring subscriptions if an isolation step removes something you needed.