- #TICKET_NUMBER
- If the reason for this PR's code changes are not clear in the issue, state value/impact
- add
- remove
- modify
- Either list QA steps or reasoning you feel QA is unnecessary
- Describe how you made sure to know that your changes worked. Should allow someone else to go verify your code without in depth knowledge.
- "Unit tested only", "tested in rdev by a, b, c, verifying feature worked by... ", "manually ran pipeline locally with these results: ..."
- Add product, design, and eng as reviewers for rdev review
- For UI changes, add screenshots/videos, so the reviewers know what you expect them to see
- For UI changes, add e2e tests to prevent regressions
- For UI changes, verify impacted analytics events still work