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

Github Pull Requests for Everyone

Github Pull Requests for Everyone

Reviewing a pull request can feel like a chore. If done poorly, PR reviews can mean a few hours of attempting to understand both the problem and the solution, then checking that the result matches the design. Sure, many of us have the luxury of walking to our coworker’s desk and getting a walk through. But what if the other dev isn’t free? What if they live in another time zone? What if you need a project manager or designer to look at your work, and they don’t have a local setup or much dev experience?

In this session, we’ll go over some tips and technologies to make your pull request process a bit smoother. We’ll discuss:
* Writing clear issues/stories to build a good foundation
* Tools you can use for reviewing work with remote coworkers
* Keeping design reviews from turning into blockers
* Adding testing instructions to your PR description
* Leaving positive feedback so no one goes home grumpy

This session is for you if your team uses Git, and….
* You have a coworker or client in a different timezone
* You regularly need a designer to review your work
* You or your coworkers work remotely one or more days a week
* You regularly contribute to open source projects (or run your own!)
* You ever have code that needs a merge, like, now

Catherine Meade

April 09, 2019
Tweet

More Decks by Catherine Meade

Other Decks in Technology

Transcript

  1. GitHub Pull GitHub Pull Requests for Requests for Everyone Everyone

    tiny.cc/cmeade-gpr-repo tiny.cc/cmeade-gpr-repo speakerdeck.com/catheraaine speakerdeck.com/catheraaine 1
  2. ✨ NEW BONUS FEATURE: ✨ ✨ NEW BONUS FEATURE: ✨

    Code Reviews Code Reviews for Everyone for Everyone tiny.cc/cmeade-gpr-repo tiny.cc/cmeade-gpr-repo 2
  3. 5

  4. RULE ONE RULE ONE No one merges their own code.

    No one merges their own code. 6
  5. RULE THREE RULE THREE If you are working with UI,

    get a If you are working with UI, get a design review. design review. 8
  6. RULE FOUR RULE FOUR If you’re working on copy, get

    a If you’re working on copy, get a copy review. copy review. 9
  7. RULE FIVE RULE FIVE Never, ever push directly to Never,

    ever push directly to master. master. 10
  8. RULE SIX RULE SIX Rules are more like… Rules are

    more like… guidelines. guidelines. github.com/sparkbox/standard github.com/sparkbox/standard 11
  9. 14

  10. Github Issue Templates Github Issue Templates via GitHub via GitHub

    tiny.cc/github-issue-templates tiny.cc/github-issue-templates 15
  11. 16

  12. 17

  13. 18

  14. Github Issue Templates Github Issue Templates via GitHub via GitHub

    tiny.cc/github-issue-templates tiny.cc/github-issue-templates 19
  15. Kasey Bonifacio, Sparkbox Developer Kasey Bonifacio, Sparkbox Developer "Writing Better

    Release Notes" "Writing Better Release Notes" tiny.cc/foundry-bonifacio tiny.cc/foundry-bonifacio 20
  16. 22

  17. 23

  18. 24

  19. We try to include: We try to include: A quick

    summary of the work being done. A link to any related stories or issues. A link or screenshot of the original design work. Step-by-step testing instructions. 25
  20. 26

  21. 28

  22. 31

  23. 33

  24. 37

  25. 41

  26. 42

  27. 43

  28. 44

  29. 45

  30. More Feedback Feedback More Feedback Feedback Offer an alternative. Phone

    a friend. Choose which hills to die on. Keep the tone light. 47
  31. 48

  32. BRYAN BRAUN, SPARKBOX DEVELOPER, EAGLE SCOUT BRYAN BRAUN, SPARKBOX DEVELOPER,

    EAGLE SCOUT "Stop Giving Depressing Code "Stop Giving Depressing Code Reviews" Reviews" tiny.cc/foundry-braun tiny.cc/foundry-braun 50
  33. “Giving positive feedback is an easy habit to adopt. You're

    already reading through the lines of code, looking for issues. It doesn't take much time to throw in a ‘Nice!’ or ‘Looks great!’ If you see something awesome, say it!” - Bryan Braun tiny.cc/foundry-braun 51
  34. ✨ Take the 2019 Sparkbox Design ✨ Take the 2019

    Sparkbox Design Systems Survey ✨ Systems Survey ✨ bit.ly/sb-2019-survey 53
  35. Thanks! Thanks! Catherine Meade Catherine Meade DEVELOPER, SPARKBOX DEVELOPER, SPARKBOX

    | [email protected] | [email protected] @catheraaine @catheraaine tiny.cc/cmeade-gpr-repo bit.ly/sb-2019-survey speakerdeck.com/catheraaine 54