Don't break work into artificially small commits. Medium to large PRs are preferred — AI quality is high enough and CI automation resolves conflicts and comments.
Any PR should include the Linear link, unit/integration tests, and have CircleCI/CodeRabbit passing.
Never push directly to master/main or staging or develop branches.
Separate BE review app (GKE) created for FE to test/implement changes — see Review Apps Guide.
API team coordinates PR merge with FE deployment.
Preview deployments:
Backend (API): Review apps are opt-in. Add the review-app label to your PR to trigger creation. Apps auto-scale to 0 after 6h of inactivity (~5 min to wake). See Review Apps Guide.
Frontend (Vercel): Preview builds are opt-in for most branches. main, develop, and staging always auto-deploy. All other branches require the deploy-preview PR label (triggers a build immediately via workflow — no push needed), [deploy] in a commit message, or the /deploy-preview Claude command. See Vercel Preview Deployments for details.
Peer review for merging PRs (someone other than the requester):
Please provide comments/screenshots/GIFs along with your PR so that the reviewer(s) can understand the intended functionality and context.
PRs should include the Linear issue link so the reviewer can track delivery.