How we handle pull requests

Give context

PR authors provide clear context: precise title, relevant links, and visuals for UI changes.

Mindful commits

Commit messages should communicate intent. We prefer conventional commit types over vague messages.

One change at a time

Small focused PRs reduce review overhead and risk. Feature flags enable incremental merges.

Stacked branches

Used selectively to avoid blocking when follow-up PRs depend on unreviewed work.

Responsibility

Review quality is shared responsibility. Feedback explains reasoning, not only rejection.

Visibility and tools

Code owners or area leads default-review when configured. Drop a link in the engineering channel when you need eyes quickly. CI runs whatever checks we have wired (lint, link check, preview deploy); issue tracker stays in sync via GitHub (labels/milestones) rather than side email threads.