How to write a good pull request description

Short summary

Write PR descriptions that answer four critical questions: what problem this solves, why this approach was chosen, how to test it, and what's explicitly out of scope. Optionally include security implications for PRs touching auth, input validation, or dependencies. Use a .github/pull_request_template.md file to make this a team standard.

• •Structure PR descriptions around four components: what, why, how-to-test, and out-of-scope
• •Include optional security section for auth, input handling, and dependency changes
• •Use PR templates to standardize the practice and reduce review friction

Generated with AI, which can make mistakes.