pull-request.link

Swap github.com for pull‑request.link

Paste a public GitHub pull request into iMessage, Slack or Discord and it unfurls as a short video: the diff, checks, reviews and the open threads, summarized. Clicking the link still takes you straight to GitHub.

GitHubhttps://github.com/oven-sh/bun/pull/30412
Sharehttps://pull-request.link/oven-sh/bun/pull/30412
  • Public repos
  • Clicks redirect to GitHub
  • Refreshes every minute
9:41
2
S
Sam
Today 9:41 AM
wait did bun really get rewritten in rust?? 🦀
lol yes. in one PR
Delivered
a MILLION lines?? who reviewed that 😭
iMessage

One card, the whole PR

What pull-request.link/oven-sh/bun/pull/30412 generates. The video steps through four chapters, then settles on a dashboard; that last frame is the og:image, for apps that show a still.

og:videoMP4 · 11 s · 960×504
og:imagePNG · the last frame
The pull-request.link card for oven-sh/bun#30412: merged, +1.01M −4,024 across 2,188 files, 78 checks passed, 3 open threads
01SummaryA one-line TL;DR of what the PR does, and what stands between it and a merge.
02ChangesLines added and removed, and the files (or, for huge PRs, directories) that carry the change.
03Checks & reviewsOne dot per CI check with the failing jobs named, and each reviewer's verdict.
04ThreadsThe outstanding discussion, paraphrased, marked open or addressed.

How it works

  1. Unfurlers get the card; people get GitHub. Link-preview bots are served og:video and og:image tags; a browser is redirected to the PR on github.com.
  2. One GraphQL call fetches the PR, its files, reviews, checks and discussion. Private repos are refused.
  3. Workers AI (DeepSeek v4.1 Flash) writes the summary, picks the threads still open and what blocks the merge. Counts come straight from GitHub.
  4. og.video's engine renders the MP4 in the Worker (Rust compositor and x264 in wasm), streams it, and caches it by content. A PR that changes gets a new video within a minute.