A pull request is not ready when the code merely works. Due diligence means treating tests, documentation, context, and review preparation as essential professional work rather than optional cleanup. section 8.2 section 8.7
Apply due diligence before and during review:
- Review your own changes and provide the context and information a reviewer needs. section 8.7
- Plan smaller features and pull requests by clarifying acceptance criteria, separating UI from business logic, or using feature flags. section 8.7
- Use review milestones, earlier reviews, or pairing when changes risk repeated rework. section 8.7
- Move repeated review debates offline, then record both the discussion and its outcome in the pull request. section 8.7
A review-ready change
Instead of submitting one large feature pull request, clarify its acceptance criteria, split the work into smaller changes, review each change personally, and give reviewers enough context to assess it efficiently. section 8.7
