Connect GitHub
Dash connects to GitHub through its own GitHub App, not the generic OAuth catalog. This gives Dash access to your repositories, pull requests, issues, releases, and code, with fine-grained controls over what it can read and write.
Install the GitHub App
Section titled “Install the GitHub App”- Go to app.dashpup.ai and open the Tools page.
- Find GitHub and click Connect.
- GitHub will ask you to choose an organization or personal account, and which repositories to grant access to. You can select all repositories or pick specific ones.
- Click Install & Authorize. You’ll be redirected back to Dash.
Only someone with admin access to the GitHub organization (or ownership of the personal account) can install the app. Once installed, all Dash workspace members can use it (unless you restrict access to specific people).
What Dash can do with GitHub
Section titled “What Dash can do with GitHub”Once connected, Dash can:
- Read code from your repos: browse files, search across repos, read specific files.
- Read and search issues and PRs: find open issues, check PR status, read review comments.
- Create issues and PRs: file a bug, open a feature request, submit code changes.
- Review PRs: leave comments, suggest changes, approve or request changes.
- Manage releases: draft release notes, create tags.
- Run GitHub Actions: trigger workflows, check run status.
How access control works
Section titled “How access control works”GitHub access follows the same two-axis model as every other Dash tool:
Who can use it
Section titled “Who can use it”The GitHub connection has an access scope:
- Workspace (default): every Dash workspace member can use it.
- Private: only the person who installed it and people they add to the allowlist.
Set this on the Tools page under the GitHub connection.
What each operation can do
Section titled “What each operation can do”Every GitHub operation has a run mode:
- Auto: runs without asking. This is the default for read operations (browsing code, listing issues, reading PRs).
- Ask: requires approval before running. This is the default for write operations (pushing code, creating issues, opening PRs, merging).
- Off: blocked entirely. The operation won’t run even if someone asks.
You can change run modes per operation from the Tools page. For example, you might set “create issue” to auto if you trust Dash to file bugs without asking, while keeping “push code” on ask.
Approval for writes
Section titled “Approval for writes”When Dash needs to push code, create a PR, or perform any write operation set to ask, it goes through the standard approval flow. The approval card shows what Dash is about to do (the branch, the commit message, the diff). You approve or deny from the card.
If a git push is held for approval, Dash will tell you and wait. The push completes automatically once approved. See How approvals work for the full breakdown.
Which repos Dash can see
Section titled “Which repos Dash can see”Dash can only access the repositories you selected during installation. To change which repos Dash has access to:
- Go to your GitHub organization’s Settings > GitHub Apps > Dash.
- Under Repository access, add or remove repos.
Changes take effect immediately.
What’s next
Section titled “What’s next”- Connect a custom MCP server if you have internal tools beyond GitHub that Dash should access.
- How approvals work for the full picture on what Dash asks about before acting.