Goal
Org admins can push feedback items to their linked GitHub repo as issues. One-click, keeps everything in sync.
Depends on: Phase 2 complete (feedback system working), #13 (detail view - where the button lives)
Prerequisites
Org has linked a GitHub repo to their Veerify project (owner, repo, personal access token with issues:write)
Store token encrypted at rest
Flow
Org admin views a feedback item ([Phase 2.3] Build feedback detail view #13 )
Clicks "Push to GitHub" button
Veerify creates a GitHub issue via API:
Title: feedback title
Body: includes description, upvote count, category, link back to Veerify feedback
Labels: maps Veerify category → GitHub label (Bug → bug, Feature → enhancement). Create label if missing.
Stores the link in github_issue_links (feedback_id ↔ issue number)
Feedback detail now shows the linked GitHub issue
Error handling
Show error if token is invalid or lacks permissions
Show error if GitHub API rate-limited (with retry suggestion)
Prevent duplicate push (check if already linked)
UI
"Push to GitHub" button on feedback detail ([Phase 2.3] Build feedback detail view #13 )
After linking: show GitHub issue link (e.g., "GitHub #42") with direct link to issue
"Unlink" option (removes the link, doesn't delete the GitHub issue)
Notes
This is one of the key differentiators - connect feedback directly to your workflow
Keep it simple for MVP - one-way push is enough
Goal
Org admins can push feedback items to their linked GitHub repo as issues. One-click, keeps everything in sync.
Depends on: Phase 2 complete (feedback system working), #13 (detail view - where the button lives)
Prerequisites
issues:write)Flow
github_issue_links(feedback_id ↔ issue number)Error handling
UI
Notes