DEV Community

Discussion on: Code Review best practices

Collapse
 
fossheim profile image
Sarah

Good tips! It's also possible in GitHub to set up templates for pull requests, which can be really useful to encourage people to include the right info.

I usually add a field for:

  • Issue the PR is linked to
  • Screenshot before & after (if it's a visual change)
  • Description of what has changed
  • Checklist (mainly unit tests, linting)

You can also link Jira to GitHub, so if you start the name of your PR with the Jira issue number, it will automatically connect the two.

Collapse
 
pandiyancool profile image
Pandiyan Murugan

Perfect!