How to Set Up GitHub
Connect your GitHub account to start creating issues from Slack
βΉοΈ Important: Individual Setup Required
Each workspace member must connect their own GitHub account individually. This ensures that issues are created with the proper permissions and attributions.
β οΈ Important: Organization Authorization & SAML
If you are connecting to repositories within a GitHub organization, please review GitHubβs documentation on OAuth Apps and Organizations .
If your organization enforces SAML SSO, you must have an active SAML session
before running the /github-setup command.
If the setup fails, visit your GitHub organization in the browser, authenticate to establish an active
SAML session, and then retry the /github-setup command.
π Prerequisites
- β Issue Pilot installed: The app must be installed in your Slack workspace
- β GitHub account: You need a personal or organizational GitHub account
- β Repository access: You must have write access to the GitHub repositories where you want to create issues
1 Connect Your GitHub Account
Follow these steps to link your GitHub account with Issue Pilot:
- Open Slack and navigate to the Issue Pilot app (find it in your Apps section or search for "Issue Pilot")
- Open a direct message (DM) with the Issue Pilot app
-
In the DM, type the slash command:
/github-setup
- Press Enter
-
Issue Pilot will send you a message in the DM with a button that says "Connect to GitHub"
π‘ Tip: The button appears directly in your DM conversation with Issue Pilot
- Click the "Connect to GitHub" button
- You'll be redirected to GitHub's authorization page
2 Authorize Issue Pilot on GitHub
On GitHub's authorization page, you'll see the permissions Issue Pilot is requesting:
Requested Permissions:
- β’ repo: Full control of private and public repositories
Why this permission?
Issue Pilot needs repository access to:
- β’ Create issues in your repositories
- β’ Verify you have access to specified repositories
- β’ Add issue labels and assignees (future feature)
- Review the permissions carefully
- If you're part of GitHub organizations, you can choose which organizations to grant access to
- Click the green "Authorize [App Name]" button
- You may be asked to enter your GitHub password or confirm with 2FA
β οΈ Organization Access: If you want to create issues in organization repositories, make sure to grant access to those organizations during authorization.
3 Confirmation
After successful authorization:
- You'll be redirected to a success page showing "β GitHub Connected!"
- The page will confirm:
- Your GitHub account is successfully connected
- Your GitHub username
- Next steps for configuration
- You can close this browser window and return to Slack
π Success! Your GitHub account is now connected to Issue Pilot. You're ready to configure your default repository.
4 Set Your Default Repository
Setting a default repository makes creating issues faster by automatically selecting which repo to use.
To set a default repository:
-
In any Slack channel, type:
/github-config owner/repo
Replace
ownerandrepowith your actual repository details -
Examples:
/github-config octocat/Hello-World/github-config mycompany/backend-api/github-config username/my-project -
Issue Pilot will verify:
- The repository exists
- You have access to it
- You have permission to create issues
- If successful, you'll see: "β Default repository set to: owner/repo"
π‘ Pro Tips:
- β’ You can change your default repository anytime by running
/github-configagain - β’ To see your current default repository, type
/github-configwithout any parameters - β’ You can override the default repository when creating issues (explained in the usage guide)
5 Verify Your Setup
To confirm everything is configured correctly:
-
Type
/github-config(without parameters) - You should see your current default repository displayed
-
If you see "Not set", run
/github-config owner/repoto set one
Quick Test:
To test that everything works:
- 1. Navigate to any Slack channel with a conversation
- 2. Right-click on a message (or click the three-dot menu)
- 3. Look for "Create GitHub Issue" in the shortcuts menu
- 4. If you see it, your setup is complete! β
π Managing GitHub Access
Viewing Authorized Apps:
- Go to GitHub.com and log in
- Click your profile picture β Settings
- In the left sidebar, click Applications
- Click the Authorized OAuth Apps tab
- Look for "Issue Pilot" in the list
Granting Additional Organization Access:
- From the Authorized OAuth Apps page, click on "Issue Pilot"
- Scroll to the Organization access section
- Click Grant next to any organization you want to give access to
- Organization owners may need to approve the request
Revoking Access:
If you need to disconnect Issue Pilot from GitHub:
- Go to the Authorized OAuth Apps page (steps above)
- Click on "Issue Pilot"
- Click the Revoke button
- Confirm the revocation
β οΈ Note: After revoking access, you'll need to run /github-setup again to reconnect.
π Working with Multiple Repositories
You can create issues in any repository you have access to, not just your default:
Three Ways to Specify a Repository:
-
1. Use your default repository
Simply use the shortcut without specifying a repo - Issue Pilot uses your configured default
-
2. Specify during issue creation
When using the shortcut, a modal will appear where you can enter a different repository
-
3. Change your default
Run
/github-config new-owner/new-repoto update your default
π§ Troubleshooting
/github-setup command not working?
- β’ Make sure Issue Pilot is installed in your workspace
- β’ Try typing the command in a different channel
- β’ Check if the app is added to the channel (invite it by @mentioning)
Can't access a repository?
- β’ Verify you have write access to the repository on GitHub
- β’ Check if the repository is in an organization that needs to approve Issue Pilot
- β’ Make sure you entered the repository name correctly (owner/repo format)
"Connect to GitHub" button doesn't appear?
- β’ The message might have scrolled up - look for Issue Pilot's response after running the command
- β’ Try running
/github-setupagain - β’ Check your Slack message settings to ensure buttons are enabled
Authorization page shows an error?
- β’ Clear your browser cache and cookies
- β’ Try using a different browser or incognito mode
- β’ Make sure you're logged into the correct GitHub account
Still having issues?
Contact our support team at [email protected]
π― What's Next?
Now that GitHub is connected, you're ready to start creating issues!
Learn to Use the Shortcut
Discover how to convert Slack conversations into GitHub issues with one click.
View Usage Guide βManage Your Subscription
Upgrade your plan for more issues per month and advanced features.
View Billing Guide β