<aside> 📌

Note: write a PR Template

</aside>

PR Guidelines — Short Version

• keep PRs small and focused

• one PR = one clear purpose

• use clear branch names and PR titles

• link every PR to the related Notion item

• describe what changed, why, and how it was tested

• include screenshots for UI changes

• get at least one review before merging

• address all review comments

• merge only tested, understandable, and relevant code

• avoid unrelated changes in the same PR

Link to DoR / DoD: Definition of Ready / Done

<aside> 📌

Pull Requests should be small, clear, and easy to review.

Every PR should have a clear purpose and be linked to the related Notion item.

</aside>

Before creating a PR

• make sure your branch is up to date
• test your changes locally
• make sure the feature or fix works as expected
• remove unused code, debug code, and commented-out code
• check formatting and naming
• update documentation if needed

PR size

• keep PRs as small as possible
• one PR should solve one clear problem
• avoid mixing unrelated changes in one PR
• prefer multiple small PRs over one very large PR

Branch naming