- Published on
GitHub Slack Copilot Works but PR Notifications Are Missing
- Authors

- Name
- Maruan
If GitHub Copilot answers you in Slack but your channel shows no pull request notifications, check the channel's repository subscription first. Picking a repo for Copilot in /github settings sets a default for Copilot work only. It does not subscribe the channel to that repo's events. If the subscription is missing, enable pull request notifications with /github subscribe OWNER/REPO pulls.
This guide covers the official GitHub app for Slack on GitHub.com. It shows how to check what a channel is subscribed to, how to add pull requests, and what to look at if alerts are still missing afterwards.
The short answer: Copilot repo defaults do not subscribe a channel to PR events
Copilot repo defaults do not subscribe a channel to PR events. GitHub's documentation says notification subscriptions and Copilot repository defaults are separate settings, and that holds in both directions. Choosing a repo for Copilot does not subscribe the channel, and subscribing the channel does not set a Copilot default.
A working Copilot proves very little. It tells you the app is installed, you are signed in, and Copilot can reach a repo. The channel still needs its own subscription before pull request events appear in it.
The documented starting point for repository events is the same one-line command: /github subscribe OWNER/REPO.
Why Copilot settings and notification subscriptions are separate
They answer two different questions. A notification subscription answers "which repository events should appear in this channel?" A Copilot default answers "which repo should Copilot work against when I ask it to do something here?" The docs describe the first as controlling which repository events appear in the channel.
Think of it as two independent switches on the same app:
/github settings -> Copilot default repo (what Copilot acts on)
/github subscribe -> channel subscription (what the channel receives)Flipping the first one never touches the second. That is why the setup feels finished. You installed the app, Copilot responds, and the channel is still silent.
The separation also works in your favor. You can mention @GitHub in a reply to a notification and hand work to Copilot from there, but that only helps once notifications are arriving in the first place.
Check subscribed repositories and active label filters
Run /github subscribe list in the channel to list subscribed repositories. If the target repository is absent, add its subscription. If it is present, explicitly enable pulls with the command below rather than assuming pull request events are enabled.
For label filters, run /github subscribe list features. GitHub documents this command as showing the channel's active label filters, not as a complete per-repository event-feature inventory. Both list commands are read-only; neither starts a Copilot task.
Subscribe the channel to pull requests with /github subscribe OWNER/REPO pulls
Run /github subscribe OWNER/REPO pulls in the channel, replacing OWNER/REPO with the real repository, for example /github subscribe acme/web-app pulls.
The /github subscribe OWNER/REPO command subscribes the channel to default notifications, including issues, pull requests, commits to the default branch, releases, and deployments, while other events require an explicit subscription. Naming pulls explicitly enables that event category. It does not remove other subscriptions already enabled for the repository.
After subscribing, run /github subscribe list again to confirm the repository is listed. A successful subscription response is a configuration check, not proof of delivery. Test with a new non-sensitive pull request or mark a draft ready for review. These are documented pulls events; there is no need to run a Copilot task. If subscribing fails, check channel membership and repository access before changing wider settings.
Two related points while you are here. You can stop alerts for one repository later with /github unsubscribe OWNER/REPO, covered in GitHub Slack unsubscribe: Stop alerts for one repository. And workflow runs use their own feature, workflows, rather than pulls, so a pull request subscription will not bring in GitHub Actions results.
If PR notifications are still missing: label filters, private repos and the wrong GitHub account
If the channel is subscribed and pull request alerts are still missing, check three things in this order.
1. Label filters. Label filters limit issue and pull request notifications to items carrying the labels you specify, so a filter can quietly hide most of your PRs. If /github subscribe list features shows a filter on the repo, remove it or label a test PR to match. Our walkthrough, GitHub Slack Label Filters Not Working? Checks and Fixes, goes through the common mismatches.
2. Private repositories. A private repo only works if the GitHub account you connected can see it and the app has been granted access to it. If subscribing to a private repo fails, check the reported error, connected identity and repository grants. Also confirm the GitHub app is present in the target channel.
3. The wrong GitHub account. Slack users authorize the app with a specific GitHub account. If you connected a personal account that cannot see the organization's repo, your subscription will not behave as expected. Reconnect GitHub to Slack: Switch Accounts Safely explains how to switch without breaking existing setup.
One more cause to rule out: draft pull requests. If your team opens most PRs as drafts, the quiet channel may be correct behavior. See GitHub Draft PR Slack Alerts: Ready for Review Checks.
Optional: GitHub and GitLab cards in one Slack workspace
Once subscriptions work, you may want a different shape of notification. MergeMe is a Slack app that shows each GitHub pull request or GitLab merge request as one card that updates in place. The official GitHub app also supports threaded updates, updating parent messages and scheduled reminders; review its native settings before switching tools.
It works with GitHub.com, GitLab.com and self-hosted GitLab connected in one Slack workspace. The Hobby plan is free forever with 1 channel mapping and 5 user mappings, and the Team plan is £5 per dev seat per month. If your team wants GitHub and GitLab cards in one workspace, try MergeMe.
Subscribe the channel first, then judge the notifications
Copilot repository defaults and channel notification subscriptions are configured separately. List subscriptions with /github subscribe list, explicitly enable pulls, and test a documented PR event. Use /github subscribe list features to inspect active label filters, then check channel membership and repository access if delivery still fails.
FAQs
Why am I not getting GitHub notifications in Slack?
Copilot repository defaults do not enable channel notifications. Run /github subscribe list to check subscribed repositories, then /github subscribe OWNER/REPO pulls to enable pull request events. If alerts remain absent, inspect active label filters with /github subscribe list features, channel membership and private repository access.
Does choosing a repo in /github settings subscribe the channel to it?
No. GitHub's documentation treats Copilot repository defaults and notification subscriptions as separate settings. Setting a default repo for Copilot does not subscribe the channel to that repo's events. You still need /github subscribe OWNER/REPO for the channel to receive notifications.
How do I see which repositories a Slack channel is subscribed to?
Run /github subscribe list in the channel to list subscribed repositories. GitHub documents /github subscribe list features for viewing active label filters, not a complete list of enabled event features. Explicitly enable pull request events with /github subscribe OWNER/REPO pulls.
Can I get GitHub Actions workflow notifications in Slack too?
Yes, but it is a separate feature. The official app supports workflow run notifications through the workflows feature, with filters for narrowing them down. A pulls subscription does not include them. See our guide on GitHub Actions Slack notifications on workflow failure for a fuller walkthrough.
Is there an alternative that shows one card per pull request in Slack?
MergeMe posts each GitHub pull request or GitLab merge request as one card that updates in place, and it supports GitHub.com, GitLab.com and self-hosted GitLab in one workspace. Hobby is free forever with 1 channel mapping and 5 user mappings; Team is £5 per dev seat per month.