Pull Request

Owner: Engineering
Reviewers: Tech Leads, QA
Status: Draft
Version: 0.1
Last Updated: 2026-09-16
Review Cycle: Per CI/process change

PR Requirements

• Target the correct branch.
• Use a Conventional Commit-style PR title.
• Describe product impact, technical change and test evidence.
• Update docs when behavior, API, data model, deployment or security changes.
• Include screenshots or recordings for visible web/mobile changes.
• Call out partial/planned behavior explicitly.

CI Gates

• Branch rules.
• Branch name validation.
• Commitlint for PR title and commits.
• Backend lint/build/test.
• Web lint/build.

Merge Readiness

A PR is merge-ready only when CI passes, review comments are resolved and release-impact notes are captured.