Summary
Keep Central Station tickets in sync with GitHub PR lifecycle and preview URLs.
3Questions
1Links
0Comments
0PRs
Open questions
- 1 Should webhook handling be GitHub App based or token/webhook-secret based for v1?
- 2 What is the canonical preview URL source for Preview Forge and future preview systems?
- 3 Should merged PRs automatically move tickets to needs-qa, ready-to-ship, or shipped?
Relationships
Related from
Central PM system
Ticket relationships/activity shipped first; GitHub PR and preview sync is the next linked Central Station enhancement.
Spec body
## Goal Central Station should automatically associate GitHub pull requests, preview URLs, and PR lifecycle events with the right tickets so the PM view stays current without manual updates. ## Desired behavior - Link opened PRs to existing tickets when the PR title, branch name, body, or labels reference a Central Station/Yawp PM item. - Create or flag placeholder tickets when an open PR has no PM association. - Show PR links and preview/deploy URLs directly on ticket detail pages. - Update ticket metadata when PRs open, close, merge, or change preview status. - Prefer webhooks for near-real-time updates; keep an hourly sync job as a backstop. ## Open product questions - Should webhook handling be GitHub App based or token/webhook-secret based for v1? - What is the canonical preview URL source for Preview Forge and future preview systems? - Should merged PRs automatically move tickets to needs-qa, ready-to-ship, or shipped?
Repo sync
No repo sync metadata recorded yet.
Activity
ticket.linked2026-05-27T15:10:28.715Zticket.created2026-05-27T13:48:37.681Z