Pull Requests - And why they're so awesome

Transcript

1. Pull Requests - and why they’re so awesome

2. Thomas Dippel Ruby Developer @ Downtown

3. Pull Requests F*cking how do they work?

4. Pull Requests F*cking how do they work? Pull requests let

   you tell others about changes you've pushed to a GitHub repository. Once a pull request is sent, interested parties can review the set of changes, discuss potential modifications, and even push follow-up commits if necessary. “ ”

5. Why should we?

6. Collaboration! - there’s no “i” in Developers, but there is

   a “ve”, which kinda looks like we...

7. Insight! - I don’t wanna miss a thing!

8. Safety! - we can’t all handle the Balmer-curve as good

   as Steve himself...

9. History! - only gives you half the story! git log

10. Things I’ve learned - and how they can optimize your

    Pull Request experience

11. Be descriptive! adjective 1 serving or seeking to describe. •

    Grammar (of an adjective) assigning a quality rather than restricting the application of the expression modified, e.g., blue as distinct from few . 2 describing or classifying without expressing feelings or judging. • Linguistics denoting or relating to an approach to language analysis that describes accents, forms, structures, and usage without making value judgments.
12. None

13. Start small Let them grow

14. None
15. None

16. Branches are free!...

17. Branches are free!... ...if you clean up after yourself.

18. pile Don’t let them pile up! pile

19. None
20. None
21. None

22. rush rush rush rush Don’t rush it!

23. Let people chime in! - and never try to assume

    control...

24. - helpfulness helps... Be constructive!

25. Have fun! - and remember to be awesome!!!

26. @dipth.com