Anatomy of a Perfect Pull Request

287

Writing clean code is just one of many factors you should care about when creating a pull request.

Large pull requests cause a big overhead during the code review and can facilitate bugs in the codebase.

That’s why you need to care about the pull request itself. It should be short, have a clear title and description, and do only one thing.

Why should you care?

  • A good pull request will be reviewed quickly
  • It reduces bug introduction into codebase
  • It facilitates new developers onboarding
  • It does not block other developers
  • It speeds up the code review process and consequently, product development

Read more at OpenSource.com