feat: add Vercel-style PR comment for deployment status

[Flo4604]

What does this PR do?

Adds PR comment deployment status reporting alongside existing GitHub commit status reporting. When deployments run for pull requests, a shared comment is created or updated with a table showing deployment status for each app/environment combination, similar to Vercel's deployment comments.

The implementation includes:

• A new prCommentReporter that manages PR deployment comments with markdown tables
• A compositeStatusReporter that fans out status updates to multiple reporters (GitHub commit status + PR comments)
• GitHub API client methods for finding PRs by branch, creating/updating issue comments, and searching for existing bot comments
• Automatic row management where each deployment gets its own table row identified by app/environment markers

Fixes # (issue)

Shows a nice comment on the stuff we deployed or failed!

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• Enhancement (small improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How should this be tested?

• Create a pull request with deployment configuration
• Trigger a deployment workflow for the PR
• Verify that a deployment comment is created on the PR with the correct table format
• Run multiple deployments for different apps/environments on the same PR
• Confirm that each deployment gets its own row in the shared comment
• Test deployment status updates (queued → building → success/failure) and verify the comment rows update accordingly

Checklist

Required

• Filled out the "How to test" section in this PR
• Read Contributing Guide
• Self-reviewed my own code
• Commented on my code in hard-to-understand areas
• Ran pnpm build
• Ran pnpm fmt
• Ran make fmt on /go directory
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues

Appreciated

• If a UI change was made: Added a screen recording or screenshots to this PR
• Updated the Unkey Docs if changes were necessary

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dashboard	Ready	Preview, Comment	Mar 17, 2026 5:32pm

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 936ccafb-ed7e-4c8e-9b8e-ab42210083ba

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/pr-deployment-comment

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Flo4604]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat: add Vercel-style PR comment for deployment status #5295 👈 (View in Graphite)
• feat: gate deployments from non-collaborators behind approval #5255 : 1 other dependent PR (#5256 )
• feat: report deployment status to GitHub Deployments API #5254
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.