pizofreude

PR Best Practices

Best Practice: Single PR for Related Changes

For all categories of changes that are closely related, they should be in one PR because:

1. Atomic Change Principle

• The main code change, tests, and documentation all serve the same purpose: e.g. Ref: Issue #619 making ItemSample publicly available
• They form a complete, logical unit of work
• Splitting them would create incomplete states in the codebase