Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Code Review and PR Tips

Code Review and PR Tips

Alexander

June 16, 2016
Tweet

More Decks by Alexander

Other Decks in Programming

Transcript

  1. Github says: Purpose Usually in the title: - This simplifies

    the display of… - This fixes handling of… Overview People may not be familiar at all with this part of code Tone In OSS the whole world can see your PR, in your company maybe too, set your tone to inform the ones you want to... Request feedback If not sure, ask for help Suggest a path Where to start if you just landed on this PR? Keep it readable Less than 400 lines is good https://github.com/blog/1943-how-to- write-the-perfect-pull-request
  2. If not follow a path, or one of the paths

    Randomly assigned person, or two of them Lead Dev / Gatekeepers Junior Develo pers
  3. Code Review Not Personal Being right is not important in

    a code review. If it works, it doesn’t mean it can’t work better Suggest Improvements, styling changes, more specific methods But don’t dictate them Just Talk Sometimes commenting on code is not enough, Reach out to your friend on Slack or pair up and explain the best solution https://blog.codinghorror.com/code- reviews-just-do-it/
  4. Summary 1. Team Motivation 2. Proper Guidelines of PR 3.

    Let everyone review 4. Make informative suggestions, or just talk