- Published on
Create GitHub issue from Slack: Commands and fixes
- Authors

- Name
- Maruan
To create a GitHub issue from Slack, use the official GitHub app: run the message shortcut on an existing Slack message, or type /github open OWNER/REPO to open a blank issue dialog. Either way you land in a form where you confirm the repository, edit the title and description, and submit.
This is the native GitHub app for Slack, not MergeMe. It has two moving parts that fail separately: your connected GitHub account, and the repository you pick. Most "the shortcut is missing" or "my repo isn't listed" reports come down to one of those two, and the sections below separate them. Copilot in Slack is a different, optional method with its own requirements, covered near the end.
The short answer: message shortcut or /github open OWNER/REPO
You have two native routes, and the choice depends on whether a Slack message already exists.
Message shortcut. Open the More actions menu on a Slack message and pick the GitHub create-issue shortcut. The app prefills the issue from that message and adds a link back to the Slack conversation.
Slash command. Type /github open OWNER/REPO in any channel. The documented behavior is that it opens an issue dialog for a title and description. An illustrative example, not a tested run: /github open acme/example.
Use the shortcut when you're converting a conversation. Use the command when you're starting an issue from scratch and want to skip the browser.
Before you start: the checks that matter (and the links to full setup)
Run three checks first. They take a minute and rule out most failures.
The GitHub app is installed in your Slack workspace. If it isn't, installation is a workspace-level step. The full walkthrough lives in the GitHub Docs guide to using GitHub in Slack, so this post doesn't repeat it.
Your GitHub account is connected. Run
/github signinin Slack. The docs describe it as the command that restarts the connect flow. Issue creation acts as you, so an unconnected account can't create anything.You can create issues in the target repository. The app requires that the signed-in account has the necessary repository access.
Notification subscriptions are a separate feature. Subscribing a channel to a repo doesn't grant you the right to create issues in it, and the docs treat defaults and subscriptions as different settings.
Create an issue from an existing Slack message, step by step
Start from the message you want to turn into an issue. The shortcut works on the selected message, not the whole thread, so pick the message that best states the problem.
Hover over the message and open More actions.
Choose the GitHub shortcut for creating an issue. If you don't see it, jump to the troubleshooting section below.
In the dialog, check the repository field. The app defaults to the repository you used last, which is convenient and also a classic way to file an issue in the wrong project.
Edit the title. A Slack message is rarely a good issue title as written.
Review the prefilled description, then optionally set labels, assignees and a milestone. The Slack issue-creation tutorial mentions adding the title, description, and relevant labels or assignees.
Submit, then open the resulting issue on GitHub to confirm it landed where you meant it to.
That last step matters more than it sounds. Slack's confirmation tells you the app sent the request. The issue page tells you where it actually lives.
Create an issue with /github open when there is no message to convert
Use /github open OWNER/REPO when the idea starts in your head, not in the channel. Replace OWNER/REPO with the full repository name, for example /github open acme/example, and the issue dialog opens with title and description fields.
Two habits keep this reliable:
Always type the repository. Don't lean on the last-used default. Typing it makes the target explicit every time.
Treat it as the fallback for the shortcut. If the message shortcut is missing in a channel,
/github openoften gets you unblocked while you sort out why. It depends on the same account and repository access, so it's a workaround, not a diagnosis.
A global shortcut is also documented as an alternative entry point. It helps when you can't right-click a specific message.
Check what the issue will contain before you share it
Read the prefilled body before you submit. Issues are often more visible than the Slack thread they came from.
When you use the message shortcut, the issue is built from the selected message and includes a link to the Slack conversation. Check three things:
Sensitive content. A message with a customer name, a token, an internal URL or a stack trace from production can end up in a repository with a wider audience than the channel had.
The Slack link. It points to a conversation that readers of a public or broadly shared repo may not be able to open. That's harmless for access control, but it leaves a dead link for outside contributors, so add the context they need in the description.
Missing thread context. Only the selected message is documented as the source. If the answer is three replies down, paste the relevant details into the description yourself.
A ten-second read here beats editing or deleting an issue after people have seen it.
Shortcut or repository missing? Separate the permission boundaries
A missing shortcut and a missing repository are different problems with different owners. Work out which one you have before changing anything.
The shortcut doesn't appear. These are checks, not guaranteed fixes:
Confirm the GitHub app is installed in this workspace and you're looking at the More actions menu on a message.
Run
/github signinand complete the connect flow. An unconnected account is the most common cause.Try
/github open OWNER/REPOin the same channel. If the command works, the app is present and the problem is narrower.Ask a Slack workspace admin whether the app is approved and available to you. Slack app approval is a workspace policy, separate from anything in GitHub.
The repository isn't listed or the issue won't submit. Think of three independent gates:
Slack app approval. Controlled by Slack workspace admins.
GitHub organization app approval. If the organization restricts third-party app access, an owner may need to approve the GitHub app for that org.
Your repository permission. Your connected account must be allowed to create issues in that repo. A fork, an archived repository or a repo where issues are disabled won't behave like a normal one.
Passing one gate says nothing about the other two. Subscribing a channel to a repo, for instance, won't give you issue-write access. If you landed here from a notification problem instead, our posts on private repo notifications and link previews not showing cover the neighboring access issues.
Copilot in Slack: an optional method with its own requirements
Copilot in Slack is a separate way to create GitHub work from a conversation. Don't confuse it with the native shortcut flow. The shortcut and /github open need only the GitHub app, a connected account and repository access. Copilot adds its own eligibility conditions on top, so check the current requirements in the GitHub Docs tutorial on creating issues from Slack before relying on it for your team.
Two practical points. If Copilot is unavailable to you, that says nothing about whether the native shortcut works, so don't troubleshoot them together. And Copilot is an addition for people who are eligible, not a replacement for knowing the two native commands, which work without it.
Once issues are sorted: keeping PRs and MRs visible in Slack
Issue creation is only half of the Slack and GitHub loop. The other half is seeing the pull requests that come out of those issues without a flood of messages.
MergeMe doesn't create or edit issues. If your team files issues from Slack and then loses the resulting PRs in channel noise, that's where it fits. Hobby is free; Team is £5 per dev seat per month.
Conclusion
Creating a GitHub issue from Slack takes two commands and two checks: the message shortcut or /github open OWNER/REPO, then a look at the repository field and the prefilled body before you submit. When something is missing, ask which gate is closed (Slack app approval, GitHub org approval, or your repo permission) instead of reinstalling everything. Once your issues are flowing, connect MergeMe from mergeme.dev to get each resulting pull request or merge request as one updating Slack card.
FAQs
How do I create a GitHub issue from Slack?
Use the official GitHub app. Open More actions on a Slack message and choose the GitHub create-issue shortcut, or type /github open OWNER/REPO to open a blank issue dialog. Confirm the repository, edit the title and description, and submit. Then open the issue on GitHub to verify it landed in the right repo. MergeMe does not create issues.
What does the /github open command do?
Per GitHub Docs, /github open OWNER/REPO opens an issue dialog for a title and description in the repository you name, for example /github open acme/example. It needs your GitHub account connected via /github signin and permission to create issues there. It is separate from channel notification subscriptions.
Why is the create issue shortcut missing in Slack?
Check that the GitHub app is installed and approved in your workspace, then run /github signin to connect your account. Try /github open OWNER/REPO in the same channel; if it works, the app is present. A Slack admin controls app approval, which is separate from GitHub organization approval and your repository permissions.
Can I set labels, assignees and milestones when I create the issue?
Yes. Fields available still depend on your repository permissions. Once the issue exists, MergeMe can show the pull requests that follow in Slack as one updating card per PR.
Is Copilot required to create a GitHub issue from Slack?
No. The message shortcut and /github open work with just the GitHub app, a connected account and repository access. Copilot in Slack is an optional, separate method with its own eligibility requirements, documented in GitHub Docs. Troubleshoot it separately from the native shortcut.