Raising a good Pull Request

Short summary

A guide to writing pull requests that teammates can actually review efficiently. Key recommendations include linking to the tracking ticket, documenting technical trade-offs, attaching UI screenshots, providing local testing steps, avoiding internal acronyms, and using a pull_request_template.md to enforce consistency. Sloppy PRs signal poor development culture and waste reviewer time.

• •Link to the tracking ticket and document trade-offs in every PR
• •Attach screenshots or videos for UI changes and provide local testing steps
• •Use a pull_request_template.md to automate and standardize PR quality

Generated with AI, which can make mistakes.