Skip to main content

First PR

A curated tiny change to prove the loop works end-to-end. Ship it on day 1 or 2.

The task​

Fix one verified documentation issue: a broken explanation, stale path, or missing cross-link. Do not add private contact details to the public site.

Yes — a docs edit. On purpose:

  • It's a real production PR against main.
  • It exercises the whole path: branch → PR → CI → review → merge → deploy → live site.
  • It teaches you the doc conventions before you touch code.

Steps​

git checkout -b docs/<short-topic>
# Edit the relevant file under docs/docs/
git add docs/docs/<path>
git commit -m "docs: clarify <topic>"
git push -u origin HEAD
gh pr create --fill --base main

Validate before opening the PR​

cd docs
npm run check

This runs the docs typecheck and production build. Apply the repository's current review and preview-deployment policy; do not assume a team name, approval count, or deployment SLA from this page.

After merge​

  • Vercel promotes the merge to production automatically.
  • Verify the deployment status in Vercel.
  • Open the changed route and confirm the public runtime reflects the merged content.

Second PR — a real code change​

When you are ready, ask the current engineering owner for a bounded starter task with an explicit test and review path.