GitHub Slack integration: how to set it up, the commands that matter, and its limits

What does the GitHub Slack integration do?

According to GitHub's integration documentation, the app does five main jobs:

• Notifications. Subscribe a channel to an organization or repository and get posts for opened, closed and reopened issues and pull requests, plus pushes to the default branch.
• Threading. Updates for each issue or pull request are grouped under one parent card that always shows the latest status, labels, reviewers and checks. Only state changes such as close or reopen are also posted to the channel.
• Actions from Slack. Create an issue from any message with the message shortcut, a global shortcut or /github open; the message text and a link back to the conversation are filled in. Issue cards have comment, edit and close buttons.
• Link previews. Links to issues, pull requests, comments, code with line numbers, repositories and users unfurl as rich previews.
• Scheduled reminders. Personal, team or organization reminders list open pull requests waiting for review at a set time, such as every morning at 10 AM.

It also supports GitHub Actions workflow notifications, where you can approve deployments and rerun failed workflows from the thread, and mentions, so you are tagged in Slack when you are an assignee or requested reviewer.

How do you set up the GitHub Slack integration?

1. Install the app. Add GitHub from the Slack Marketplace. If your workspace requires app approval, a Slack admin approves it first. On Slack Free, it counts toward the 10-app limit.
2. Link your account. Run /github signin and authorize GitHub. Choose all repositories or a subset; if you pick a subset, the app prompts you when you subscribe to a new one.
3. Add it to private channels. The app is enabled in public channels after install. For a private channel, run /invite @github.
4. Subscribe. In the channel, run /github subscribe owner/repo, or /github subscribe owner for a whole organization.
5. Trim the noise. Turn off what the channel does not need and add a label filter (below).

GitHub Enterprise Cloud with data residency uses a separate app, and GitHub Enterprise Server supports Slack from version 3.8.

Which /github commands and filters matter most?

Source: GitHub integration for Slack, checked October 30, 2026.

Two details trip people up. Only one label filter is supported per subscription; entering a new one replaces the old one. And comments and reviews appear only inside the issue or pull request thread unless you subscribe with comments:"channel" or reviews:"channel".

What can @GitHub Copilot do in Slack?

In August 2026 GitHub brought Copilot's agent into the Slack app in public preview. Mention @GitHub in a DM, channel or thread and it can answer questions about your code and GitHub activity, triage bugs, create and label issues, investigate failures, and open a pull request with a link back to the conversation. It can also create a dedicated Slack Code channel for a task. An October 15 update added work across multiple repositories in one conversation.

The new experience is available to organizations on Copilot Business and Copilot Enterprise, and usage counts against existing Copilot entitlements. An admin must enable the Copilot cloud agent policy. Copilot acts with the permissions of your linked GitHub account and, per GitHub's docs, captures the whole Slack thread as context, so use a DM if a thread contains things that should not end up in a pull request.

What does the GitHub Slack integration not do?

• No summaries. It posts events as they happen. It will not tell a stakeholder on Friday what shipped this week, what slipped and what is blocked.
• Noise at scale. A busy repository with commits and comments turned on can bury a channel. Most teams keep a separate notifications channel per repository.
• Previews have rules. Links do not unfurl if the same link was shared in the last 30 minutes, if a message has three or more links, or if the repository is private and the sharer has not signed in or the app is not in the channel.
• No other tools. It only knows GitHub. If your update needs Linear issues, a Google Sheet of metrics or a client email, someone still stitches them together.
• Copilot needs a paid Copilot plan. The agent features are not part of the free notification app.

How do you get a weekly GitHub summary in Slack?

There are three common ways. A scheduled script can call the GitHub API and post merged pull requests and closed issues to a channel; it is precise but someone has to maintain it. Slack Workflow Builder can post a reminder for someone to write the update, but it cannot read GitHub on its own (see Workflow Builder examples). Or an AI agent in Slack can read the repository and draft the update in plain language for a person to check.

Geniusly is an AI coworker for your team in Slack. It reads the accounts you connect (Gmail, Google Drive, Google Sheets, Slack, GitHub, Linear, and Google Ads) and prepares a brief, report, status update, or handoff for a person to review. Connected apps are read-only by default, except Google Sheets edits you explicitly ask for, and Slack messages beyond its reply are posted only after your approval. Anyone in a channel it has been invited to can ask it for work, it can run a task once, daily, or weekly, and it has a Free plan. Its GitHub connection is read-only: it reads repository activity to draft updates and handoffs, and it does not create issues or pull requests. Our guide to turning a Linear or GitHub week into a stakeholder update shows sample output, and the integrations page lists what each connection can access. Keep the GitHub app for real-time alerts and use a summary for the people who do not live in the repository. You can try Geniusly free.

Frequently asked questions

Is the GitHub Slack integration free?

Yes. The GitHub app for Slack costs nothing to install and use for notifications, link previews and issue actions. On the Slack Free plan it counts toward the 10-app limit. The @GitHub Copilot agent features need a paid Copilot plan.

How do I subscribe a Slack channel to a GitHub repository?

Invite the app to the channel if it is private with /invite @github, sign in with /github signin, then run /github subscribe owner/repo. Add features such as reviews or workflows after the repository name.

Why is my GitHub Slack integration not posting?

Common causes are a private channel the app was not invited to, a repository not included in the app's GitHub installation, a label filter that excludes the events, or features that are off by default, such as comments, reviews and workflows.

Can I get GitHub Actions notifications in Slack?

Yes. Run /github subscribe owner/repo workflows. By default it covers workflows triggered by pull requests to the default branch, and you can filter by workflow name, event, branch or actor. You can approve deployments and rerun failed workflows from the thread.

Can GitHub post a weekly summary to Slack?

Not by itself. The integration posts individual events. For a weekly summary you need a script against the GitHub API, or an AI agent that reads the repository and drafts the update for review.

Does @GitHub in Slack use my permissions?

Yes. Copilot in Slack acts with the permissions of your linked GitHub account, and it can only create issues where you already have permission. Repository admins can require an extra approval before pull requests from the Copilot app can merge.