- Published on
GitHub Slack Link Previews Not Showing: Checks and Fixes
- Authors

- Name
- Maruan
When a GitHub link has no preview, check five things in order: the workspace setting that allows link previews, whether the same link was already shared in that channel recently, whether the message contains three or more links, whether you have connected your GitHub account, and, for private repositories, whether the GitHub app is a member of the channel. This article covers the official GitHub app for Slack on GitHub.com.
Previews and notifications are two separate systems. A preview is what Slack shows when someone pastes a URL. A notification is what a repository subscription posts on its own. Fixing one does nothing for the other, so each check below has a clear pass or fail branch and a safe way to test it without pasting anything sensitive.
Quick answer: the five things to check when a GitHub link has no preview
Run these in order. Each one rules out a cause the GitHub documentation lists.
Link type. Is it a PR, issue, linked comment, code blob with line numbers, or an organization, repository or user page? For other URL shapes, check current documentation before treating a missing preview as a fault.
Workspace setting. Link previews can be disabled for the whole Slack workspace. Check whether previews for github.com have been disabled.
Suppression rules. The same link shared in the same channel in the past 30 minutes does not unfurl again. A message with three or more links does not unfurl either.
Your GitHub connection. For private repository links, the person pasting needs a GitHub connection, and must not have declined the preview prompt.
Bot membership. For private repository links, the GitHub app has to be in the channel.
The first three apply to public links too. The last two matter only for private repositories.
If you take one habit from this article, take this: change one variable at a time. Pasting five links into three channels at once tells you nothing, because the three-link rule and the repeated-link rule will both fire and hide the real cause.
Pasted-link previews are not repository subscriptions
A repository subscription is something you create with /github subscribe. It tells the app to post events (PRs, issues, pushes, workflows) to a channel without anyone pasting anything. A link preview is something Slack triggers when a person pastes a GitHub URL, and the app answers by supplying the card.
They use the same app but have separate settings and diagnostic checks. You can have a repository subscribed to ten channels and still see bare URLs when someone pastes a link. You can also have zero subscriptions and get perfect previews. Do not change repository subscriptions until you have checked the documented preview controls.
So take a position before touching any settings: diagnose pasted-link previews separately from event subscriptions. If your symptom is "nothing posts by itself," you have the reverse problem, and Fix GitHub Slack Private Repo Notifications covers it. If your symptom is "I pasted a link and it stayed bare," stay on this page.
A useful sanity question for your team: did the card appear because someone pasted a link, or because an event fired? Answer that before anyone changes a subscription.
Where are GitHub Slack alerts configured, and is it the same as link previews?
No, they are configured separately. Alerts are set per channel with /github subscribe, and you choose event types such as issues, pulls, commits, releases and workflows. Link previews (unfurls) are controlled by the GitHub app's preview setting and Slack's own unfurl behavior. A channel can have full alerts and no previews, or the reverse. So a missing preview card tells you nothing about whether your subscriptions are set up correctly.
Confirm the link type is one the GitHub app unfurls
The GitHub app unfurls a specific list of URL shapes, per its documentation:
Pull requests
Issues
Directly linked comments (the URL with the comment anchor)
Code blobs with line numbers
Organizations, repositories and users
That list is narrower than people assume. A bare file URL without a line reference is a different shape from a blob link with line numbers. Actions run, commit and release pages are not on that documented list. This omission does not establish every unsupported URL or prove that a particular failure is expected.
Do this check first because it costs nothing and ends a lot of investigations quickly. Open the URL in a browser, look at the path, and match it against the list.
Pass: the URL is a PR, issue, linked comment, line-numbered blob, or org/repo/user page. Move on to the suppression checks.
Fail: the URL is outside that list. Test a documented supported link first, and inspect current app documentation for the original URL type.
One practical tip: when sharing a code reference, copy the permalink with the line numbers selected in GitHub rather than the plain file URL. Selecting lines before copying produces the blob-with-lines shape the app recognizes.
Rule out suppression: workspace setting, repeated link, three or more links
Three documented rules can silence a preview even when everything is connected correctly.
Workspace link previews disabled. Slack lets a workspace turn link previews off. If it is off, the GitHub app cannot show a card. GitHub's docs point to Slack's own documentation for this setting, so confirm the exact menu wording in Slack's current help pages instead of trusting a screenshot from an old blog post. Ask a workspace admin to check it. Test by pasting a different public link type, such as a public repository URL. If other apps' links also stay bare, investigate Slack preview settings; that observation alone does not isolate the cause.
Repeated link. If the same link was already shared in the same channel in the past 30 minutes, it does not unfurl again. This is documented suppression, not a delay and not a speed guarantee. The classic trap: you paste a link, see the preview, delete the message, and paste it again to "retry." The second paste is suppressed. Wait out the window or test with a different URL.
Three or more links in one message. A message containing three or more links does not unfurl. Release notes and standup summaries hit this constantly. Test one fresh supported link in a message on its own, then check the other documented conditions if the preview is still absent.
Pass or fail: if any of the three applies, you have your answer without touching GitHub at all. If none applies and a supported public link still lacks a preview, record the app installation, affected channel, link type and test time for your workspace admin or GitHub support. These checks do not exhaust every possible fault.
Private repository links: GitHub connection, preview prompt and bot membership
The documented preview-suppression rules list three private-repository conditions: the user has not connected their GitHub account, opted not to show previews, or the GitHub app is not in the channel. A preview for a private link can expose repository details to everyone in the channel, which is why the app gates it.
The sharing user has no GitHub connection. The person who pasted the link must have connected their GitHub account to the app. Run /github signin in Slack and complete the flow. Without it, the app cannot verify access, so it shows nothing.
The user declined the preview prompt. For private links the app asks the sharer whether to show the preview. If someone dismissed or declined that prompt, the link stays bare. Paste a new, different private link and answer the prompt deliberately.
The GitHub app is not in the channel. The app needs to be a member of the channel where the link is pasted. Run /invite @github in that channel, as documented. Check membership in the actual affected channel, rather than relying on another channel where the app works.
Security caution: before testing, confirm the channel membership is appropriate for the repository. Do not paste a private link into a wide-open channel just to see whether it works. Use an existing private channel where those members already have legitimate access.
Pass: after sign-in, accepting the prompt and inviting the app, a fresh private link unfurls. Fail: go back to the suppression checks, because a repeated or multi-link message will still be silenced.
How do I set up the GitHub Slack bot?
Install the GitHub app from the Slack App Directory, which needs a Slack workspace admin or someone with install rights. Then run /github signin to connect your GitHub account, and authorize access to the organizations you need. For private repositories, invite the bot to the channel with /invite @GitHub and confirm the GitHub app can access that repository. Once connected, previews for private links and /github subscribe commands should work in that channel.
A safe test sequence with expected pass/fail outcomes
Use these example steps in an approved test channel. Adapt the policy to your team. Never paste real private source snippets into a public test channel.
Test 1: one public PR URL, alone in a message. Pick a public PR you have not pasted in that channel in the last 30 minutes. Expected: a preview card. If it appears, link type, workspace setting and app installation are fine. If it does not, check the workspace setting before anything else.
Test 2: the same URL again, immediately. Expected: no preview. That confirms the repeated-link rule is behaving as documented, and it tells you your earlier "retry" failures were suppression, not breakage.
Test 3: a different public URL plus two more links in one message. Expected: no preview. Three links in one message is documented suppression. For the single-link follow-up, use a different public PR URL not shared in that channel in the past 30 minutes, so the earlier test does not introduce repeated-link suppression.
Test 4: one non-sensitive private link in an appropriate existing private channel. Run /github signin first if needed, answer the preview prompt, and make sure the app is in the channel with /invite @github. Expected: a card. If the card is missing, walk the three private checks in order.
Read the outcomes as a decision tree. Test 1 failing points at settings or the app. Tests 2 and 3 passing as "no preview" are good news. Test 4 failing points at connection, prompt or membership.
This sequence does not prove anything about visibility rules beyond what you observed, and it does not promise a fixed timing for cards to appear. It isolates which documented rule is in play.
When previews work but notifications don't (and the reverse), plus where MergeMe fits
Keep a two-column mental model. Previews answer "what is this link?" Notifications answer "what just happened?"
Previews work, notifications don't. The pasted-link path is healthy, but no repository subscription is delivering events to the channel. Fix subscriptions, filters and channel membership. The article on review comments not showing covers the review and comment event side, and the private repo notifications guide covers delivery for private repositories.
Notifications work, previews don't. Subscriptions are fine, and the problem is one of the five checks above. Don't touch the subscriptions.
MergeMe provides one updating Slack card per GitHub pull request or GitLab merge request. This is separate from the official app's pasted-link preview feature.
Conclusion
Stop treating a bare URL as a subscription problem. Walk the five checks in order, change one variable per test, and keep a short note of which rule fired, because the next person to see a bare link will hit the same one.
If the real gap on your team is that PR status is hard to find once the link scrolls away, fix that with a card, not a preview. Connect GitHub.com and Slack to MergeMe's free Hobby plan (one channel mapping, five user mappings), map your review channel, and open a test pull request. You will get one Slack card for that PR that updates as it moves, which is the thing people were pasting links to get in the first place.
FAQs
Why are my GitHub links not unfurling in Slack?
The GitHub app documents these causes: workspace link previews are disabled, the same link was shared in that channel in the past 30 minutes, or the message has three or more links. For private repositories, also check your GitHub connection, the preview prompt and whether the app is in the channel.
Do I need to run /github subscribe to get link previews?
Repository subscriptions and pasted-link previews have different controls. Check the documented preview settings, repeated-link and multi-link suppression, and private-link connection, prompt and bot membership before changing subscriptions.
Why does a GitHub link only unfurl once in Slack?
The GitHub app documents that a link already shared in the same channel in the past 30 minutes will not unfurl again. This is suppression, not a bug. Delete-and-repost does not help. Wait out the window, or test with a different URL. See the [integrations/slack README](https://github.com/integrations/slack) for the rules.
Which GitHub links does the Slack app preview?
GitHub documents previews for pull requests, issues, directly linked comments, code blobs with line numbers, and organization, repository and user links. For other URL shapes, consult current documentation; omission from this list alone does not establish whether a missing preview is a fault.
Can I turn GitHub link previews off in Slack?
Check the current Slack preview preferences and any workspace restrictions for github.com. Preview settings and repository subscriptions are separate controls, so diagnose missing pasted-link previews separately from automatic event delivery.