11 Ways to Create Pull Requests that are Easy to Review
hackerone.com | blog | #code-review | #best-practices | #pull-request | #software-engineering | #unit-testing
Summary
Eleven habits for review-friendly pull requests: keep them under 500 lines, enforce consistent style with linters, write self-documenting code, unit tests, and intent comments.
- Published
- Collected
--- id: 2939 title: "11 Ways to Create Pull Requests that are Easy to Review" source_domain: hackerone.com source_url: "https://www.hackerone.com/blog/11-ways-create-pull-requests-are-easy-review" published_at: "2020-10-21T01:00:00Z" tags: ["code-review", "best-practices", "pull-request", "software-engineering", "unit-testing"] phying_url: "https://phying.com/item/2939" lang: en --- # 11 Ways to Create Pull Requests that are Easy to Review ## Summary Eleven habits for review-friendly pull requests: keep them under 500 lines, enforce consistent style with linters, write self-documenting code, unit tests, and intent comments. ## Intelligence Metadata - **Sources:** hackerone.com - **Published:** 2020-10-21T01:00:00Z - **Original:** https://www.hackerone.com/blog/11-ways-create-pull-requests-are-easy-review - **Phying News:** https://phying.com/item/2939