Connect GitHub in three steps
Install the GitHub App
Connect your organization or repositories to Viably from the dashboard's GitHub power. The GitHub App scopes access to only the repos you select.
Set a default channel
Choose a default Slack channel for GitHub activity under the GitHub section of the Powers dashboard. Every event type falls back to it unless overridden.
Tune with /github-notify
Run /github-notify in Slack to see your current subscriptions and route individual event types to specific channels.
Route events to the right channels
/github-notify shows every event type and the channel it posts to. Send PRs to #code-review, failed builds to #ci, and issues to your triage channel — each independently, with a workspace default as the fallback.| Event type | What you get |
|---|---|
| 🐛Issues & Comments | Opened, closed, and commented issues from your connected repositories. |
| ⤴️Pull Requests & Reviews | PR activity and review submissions, so code review stays visible in Slack. |
| 🚀Pushes | Commits pushed to the branches you care about. |
| ⚙️Workflow Runs | CI/CD workflow results — know when a build or deploy passes or fails. |
Two-way issue sync
File from Slack
Turn a Slack message into a tracked issue and, when GitHub is connected, it’s created on the repo as a real GitHub issue. See the Issue Tracking guide for the full flow.
Per-repo control
Issue creation is enabled per repository, so you decide exactly which repos can be written to from Slack — every issue picker respects that setting.
Stays in sync
Updates on the GitHub side flow back to Slack through your routed channels, keeping both surfaces consistent without manual copying.