GitHub
Slack reactions, GitHub issues.
React 🐛 on any message and Viably opens a GitHub issue in the linked repo — title, body, and link back to the thread. Status flows both ways.
Issues — synced to GitHub
Checkout 500s on annual plan switch
viably/on_next·#218
Reminder DST off-by-one
viably/on_slack·#214
OCR drops multi-line receipts
viably/on_bullmq·#207
Capabilities
What you can do
Two-way sync
Close an issue on GitHub and it resolves in Slack; resolve it in Slack and the GitHub issue closes.
Per-repo controls
Link multiple repos and choose exactly which ones can receive new issues from each workspace.
AI triage
Ask @Via to turn a noisy thread into several well-scoped issues, each filed to the right repo in one shot.
In Slack
Filed straight from Slack
#product — Slack
Today
KM
Kevin10:42 AM
Checkout is throwing a 500 on the annual plan switch 😬
ViaApp10:42 AMGitHub
🐛Issue #218 created
- Repo
- viably/on_next
- Assignee
- @oscar
- Priority
- High
- Status
- Open
Flow
How it works
1
Link your repositoriesInstall the GitHub App from the command center and pick which repos Viably can write issues to.
2
React 🐛 or ask @ViaAdd the bug reaction to any message, or mention @Via to file one or many issues from a conversation.
3
Stay in syncViably keeps Slack and GitHub aligned — assignees, status, and links update on both sides.
Ready when you are
Assemble your operating system inside Slack.
Add Viably free. Turn on the powers your team needs, when you need them.
SignalRecordOwned work
- Free to start
- The free plan needs no card
- Powers on when you need them