Welcome! Before opening a pull request or raising an issue, please take a moment to review our Best Practices Guide. It covers our GitHub workflow, PR guidelines, the PR & QA verification process, code quality standards, and more.
- Use the PR template - it's applied automatically when you open a PR.
- Keep PRs small and focused (see the Best Practices Guide for size guidelines).
- Once your PR is merged, move the ticket to the QA Verification column yourself.
- Never include secrets, API keys, or credentials in a PR description or diff - see the Secrets & Credentials section of the Best Practices Guide.
Choose the issue template that matches what you're reporting:
- Defect Report - general bugs found during QA or development.
- UI Defect Report - visual/UI mismatches against the Figma design.
- QA Verification - used as a sub-issue to verify a merged PR (or a fixed defect) on a live environment.
If anything is unclear, check the Best Practices Guide first, then reach out to your PM or lead.