Developer Documentation
PR Review Guide
Pull requests must explain what changed, why it changed, UI screenshots when relevant, migration notes, test evidence, documentation updates, security impact, rollback notes, and w
Use this when you need detailed reference information for Developer Documentation.
Pull requests must explain what changed, why it changed, UI screenshots when relevant, migration notes, test evidence, documentation updates, security impact, rollback notes, and whether secrets or integrations were added.
Reviewers should use the checklists in .github/ for code review, migration, security, documentation, testing, and release readiness. UI hiding is not authorization; server-side checks remain required for protected data and actions.
Developer Details
- Source
- apps/docs/content/engineering-quality/pr-review-guide.md
- Owner
- Module Owner
- Status
- Current
- Module
- Developer Documentation
- Related route
- None