MergeMe logoMergeMe
Published on

GitHub Slack unsubscribe: Stop alerts for one repository

Authors
  • Name
    Maruan

To stop the official GitHub Slack app posting about one repository, run /github unsubscribe OWNER/REPO in the channel where the alerts appear. That removes that repository's subscription from that channel only. The app stays installed, your GitHub authentication stays connected, and every other subscription keeps working.

The command is short, but the channel is shared, so the change lands on everyone in it. This guide covers the exact syntax, how a full unsubscribe differs from switching off selected event types and from muting the channel in Slack, how to record your settings first so you can undo the change, and what to check when messages keep arriving afterwards.

The short answer: /github unsubscribe OWNER/REPO in the affected channel

Type the command in the channel that receives the unwanted messages, replacing OWNER/REPO with the repository's full name:

/github unsubscribe OWNER/REPO

For example, /github unsubscribe acme/billing-api removes that repository from the channel you ran it in. The command is scoped to the channel, so the same repository keeps posting in a different channel until you run it there too. The official app documents this under Subscribing and Unsubscribing.

You don't need to uninstall the app, remove it from the workspace or sign out of your GitHub account. Those steps are far bigger than the problem and would break subscriptions other people rely on.

Three different things: full unsubscribe, event-level unsubscribe, muting the channel

A full unsubscribe removes the repository's subscription from the channel, so it stops posting there. An event-level unsubscribe keeps the subscription but switches off named event types. Muting the channel is a Slack setting that hides notifications for you and changes nothing for anyone else.

Full unsubscribe. /github unsubscribe OWNER/REPO. Use it when nobody in the channel needs this repository's activity.

Event-level unsubscribe. Add the event name: /github unsubscribe OWNER/REPO commits reviews comments. Use it when the pull request and issue messages are useful but commit chatter isn't. GitHub lists notifications enabled by default and disabled by default in its customization guide.

Muting the channel. This is Slack's own per-user control. It quiets your view of the channel and leaves the subscription running for everyone else, so it's the right choice when the problem is only your attention, not the channel's contents.

Pick the smallest change that fixes the actual complaint. If the noise is one event type, don't remove the whole repository.

Before you change anything: run /github subscribe list and record current features

Run /github subscribe list in the channel first and copy the output somewhere you can find it. It shows what the channel is subscribed to, including the features enabled on each repository.

That record is your way back. A subscription can carry enabled events, branch filters for commits and label filters for issues and pull requests, and none of that is obvious from the channel itself. Once you unsubscribe, you're rebuilding from your notes, not from the app.

Because the channel is shared, tell its owners before you run anything. A quick message such as "removing acme/billing-api alerts from this channel, let me know if you still need them" costs nothing and saves someone from discovering the silence a week later when a review goes unnoticed.

Stop one repository, or only selected events, step by step (and how to reverse it)

Work through these steps in the affected channel.

  1. Run /github subscribe list and record the repository's current features.

  2. Decide between a full unsubscribe and an event-level one.

  3. For a full removal, run /github unsubscribe OWNER/REPO.

  4. For selected events only, run /github unsubscribe OWNER/REPO followed by the event names, for example /github unsubscribe OWNER/REPO commits.

  5. Run /github subscribe list again and confirm the change shows up.

  6. Trigger a fresh test event, such as a new pull request or a comment, and watch whether anything posts. Don't judge by old messages, and don't expect the result at a guaranteed moment.

To reverse an event-level change, swap the verb: /github subscribe OWNER/REPO commits turns commits back on. To reverse a full unsubscribe, run /github subscribe OWNER/REPO in the same channel. Both directions use the documented command format.

If your real problem is commit noise from particular branches, a branch filter fits better than dropping the repository. See GitHub Slack branch filters for how those work.

Why restoring defaults is not the same as restoring custom filters

Resubscribing gives you the default feature set, not the exact configuration you had before. If the old subscription had a branch filter on commits or a label filter on issues and pull requests, running /github subscribe OWNER/REPO again doesn't bring those back.

Defaults and customizations are separate. GitHub documents one list of notifications enabled by default and another of notifications disabled by default, and filters sit on top of both. A removed filter has to be created again with its own command.

This is why the earlier record matters. Compare the output of /github subscribe list before and after, then re-apply any filter or non-default event you had. Treat the first list as the source of truth, not your memory of how the channel behaved.

Still getting messages? Check separate channels, other apps, workflow webhooks and personal reminders

If something still posts after you unsubscribe, assume a different sender before you assume the command failed. Unsubscribing removes one subscription in one channel. It doesn't silence every route GitHub activity can take into Slack, and it doesn't promise that every thread update stops.

Check these in order:

  • Other channels. The same repository may be subscribed in another channel, or in several. Run /github subscribe list in each place you see alerts.

  • Other apps. A second integration, a custom bot or an older connection can post about the same repository independently of the official app.

  • Workflow webhooks. A GitHub Actions step or an incoming webhook can post to Slack on its own. Those messages come from your workflow files, not from the app's subscriptions. See GitHub Actions Slack notifications on workflow failure for how those are wired.

  • Personal reminders. Reminders are separate from channel subscriptions. If they arrive in a DM, adjusting the channel won't touch them.

  • Workflow subscriptions. The app can also subscribe a channel to workflow run notifications, which are configured separately from repository events.

Identify the sender from the message itself, then change that source. Running the command again won't help.

If you want one updating card per pull request instead (optional)

If the real complaint is that pull request activity fills the channel, removing the repository is a blunt fix. The alternative is to change how the activity is shown.

The official GitHub Slack app already threads pull request updates and updates the parent message. MergeMe shows GitHub pull requests and GitLab merge requests as one updating Slack card per PR or MR, with GitHub.com, GitLab.com and self-hosted GitLab supported in one workspace. It is optional and is not needed to unsubscribe.

Remove the smallest thing that stops the noise, and write down what you changed

Run /github subscribe list, record it, then use /github unsubscribe OWNER/REPO in the affected channel, or add event names if only some alerts are the problem. Leave the app installed and your authentication connected.

FAQs

How do I unsubscribe from a repository in the GitHub Slack app?

Run /github unsubscribe OWNER/REPO in the channel that receives the alerts. This removes that repository's subscription from that channel only. The app stays installed and your GitHub authentication is untouched. Run /github subscribe list first to record the current features, so you can restore them later.

Can I stop only some events, such as commits, for one repository?

Yes. Add event names to the command, for example /github unsubscribe OWNER/REPO commits reviews comments. To turn them back on, replace unsubscribe with subscribe. This keeps the repository subscribed while switching off the event types you do not want in the channel.

Is unsubscribing the same as muting the Slack channel?

No. Unsubscribing changes the app's subscription for everyone in the channel. Mute if only your attention is the problem, and unsubscribe when the channel itself should stop receiving that repository's activity.

Does unsubscribing stop GitHub emails too?

No. The `/github` slash command also interacts with GitHub—for example, creating issues and pull requests—and is not limited to managing channel subscriptions. GitHub emails are controlled by your notification settings on GitHub, and Slack's own account is managed separately. Removing a repository from a channel does not change either of those, and it does not touch other apps or workflow webhooks posting to Slack.

Will resubscribing bring back my old filters?

Not automatically. That is why recording /github subscribe list before you unsubscribe matters. If you want a different way to see pull request activity, MergeMe shows each PR as one updating card.