The "link-in-bio" for your GitHub pull requests. Curate your proudest PRs, showcase your expertise, and stand out — with a single shareable link.
myprs.dev · myprs.dev/your-github-username
Your best work as a developer often lives in pull requests scattered across other people's repositories — invisible on your GitHub profile. MyPRs pulls them together on one page you can put in your bio, resume, or job application.
- Instant profile — visit
myprs.dev/<username>and your merged PRs are already there. No setup required. - Curate what matters — sign in with GitHub to feature your proudest PRs and hide noisy repositories.
- Built to share — clean link, rich social cards with per-profile OG images, and a one-click share button.
- Looks good everywhere — responsive, dark mode, GitHub contribution chart included.
- Open
myprs.dev/<your-github-username>— merged PRs load straight from the GitHub API. - Continue with GitHub to claim your profile.
- Star ⭐ PRs to feature them at the top; filter out repositories you don't want shown.
- Share your link.
- Next.js 16 — App Router, React Server Components, Server Actions
- React 19 · Tailwind CSS 4 · shadcn/ui
- Supabase — GitHub OAuth via
@supabase/ssr, Postgres with RLS - Vercel — hosting and preview deployments
bun install
# local Supabase (Docker required); prints the URL + anon key
supabase start
cp .env.example .env.local # fill in the values from `supabase start`
bun run dev # http://localhost:3000Optionally set GITHUB_TOKEN in .env.local to raise the GitHub API rate
limit. npm works everywhere bun is shown.
Other scripts: bun run build, bun start, bun run typecheck, bun run lint.
Deploys to Vercel with zero config — Next.js is auto-detected. Set the
environment variables from .env.example (NEXT_PUBLIC_* plus
GITHUB_TOKEN) in the Vercel project settings.
Issues and PRs are welcome. If you ship something you're proud of — feature it on your MyPRs.