Triage from GitHub Issues
Pipe GitHub Issues into your project's Triage queue using a label, and let SprintVibe post status updates back as comments on the issue.
How it works
- Enable triage for a linked GitHub repo (Project → Context tab → Codebase → Triage from GitHub Issues)
- Pick a label (default:
triage) - Apply that label to any GitHub issue you want triaged
The issue title, body, and submitter are pulled into a triage item with source: github and a stable external_id like github:owner/repo#42. Re-deliveries are deduped automatically.
What triggers a sync
| GitHub event | What happens |
|---|---|
| Issue opened | If the issue already has the triage label, item is created. |
| Label added | If the added label matches your triage label, item is created (or updated). |
| Issue edited | Title/description on the existing triage item is updated. |
| Triage label removed | The triage item is auto-declined ("Triage label removed on GitHub"). |
Bidirectional comments
When a triage item is acted on inside SprintVibe, a comment is posted back to the originating GitHub issue:
- Accepted → ✅ comment with the new backlog story title
- Declined → ❌ comment with the decline reason (if provided)
- Marked duplicate → 🔁 comment with the linked story title
GitHub App setup
The SprintVibe GitHub App must subscribe to the Issues event in its webhook configuration alongside Pull request, Push, and Installation. If you self-host or fork SprintVibe, update your GitHub App's Permissions & events settings to include Issues (read & write — write is required for posting comments back).
Tier requirements
GitHub-sourced triage requires the same Pro or Teams subscription as GitHub Integration overall. Hobby users see the integration locked.