Github and the Software Startup

Transcript

1. GITHUB AND THE SOFTWARE STARTUP The First Month. Nathan Hughes

   @ndh313

2. THE LEAN SOFTWARE STARTUP Pay for what you need, and

   nothing else.

3. CHEAPNESS IS A SURVIVAL TRAIT

4. DAY ONE What’s the problem?

5. WHY GITHUB?

6. SMALL & NIMBLE SOURCE CODE IS IMPORTANT WORKFLOW IS IMPORTANT

   SOCIAL SHARING ALIGNS

7. WEEK ONE What’s the problem?

8. KEEPING SECRETS Private and public repositories

9. KEEPING SECRETS SECRET SSH Public and Private Keys

10. GETTING YOUR STUFF INTO GITHUB

11. SO WHERE DO YOU START?

12. LONE WOLF WORKFLOW

13. Your Laptop github.com origin master local master Start Work End

    Work git commit git add git clone git push 1 1 1 2

14. WEEK TWO What’s the problem?

15. GETTING YOUR STUFF ONTO OTHER SERVERS

16. DEPLOY KEYS

17. Your Laptop github.com origin master local master Start Work End

    Work git commit git add Your Staging local master git clone 1 1 git push git pull 1 2 1 3

18. WEEK THREE What’s the problem?

19. ORGANIZATIONS AND TEAMS

20. ONE LESS SHORTCUT git pull: out. git fetch and git

    merge: in

21. STANDARD PRACTICES fetch and merge from master often integrate often

22. MASTER REPOSITORY What the organization owns, aka upstream.

23. PERSONAL FORKS Yours, your new origin.

24. YOUR NEW WORKFLOW Work in your fork, send Pull Requests

    to the Master

25. Your Laptop github.com Master Repo (upstream) master local master Start

    Work End Work git commit git add Fork Repo (origin) master git clone git push Merge Pull Request Fork 1 1 1 2 1 3 1 4 1 5

26. BUT WHY? Two good reasons.

27. GRANULAR CHANGES Answering “what in the ***** happened?” since 2008.

28. CODE REVIEW The practice you can’t afford to skip.

29. KEEP IT. IF YOU CAN. Personal Forking and Pull Requesting

    is a clean, simple, versatile workflow. It can work for a long time.

30. WEEK FOUR Success breeds complexity!

31. OH, YOU’RE HAVING PROBLEMS You don’t say. What a mess.

    How interesting.

32. HARD DECISIONS Feature Branches? Per Developer Branches? Something Else? Dedicated

    Build Managers?

33. BECAUSE WE ARE small, experienced, co-located, self-managing, WE’LL TRY FEATURE

    BRANCHES
34. None

35. FEATURE BRANCHES

36. Your Laptop github.com Master Repo (upstream) master Start Work git

    commit git add Fork Repo (origin) git clone git push -u origin feature Merge Branch Branch Pull Request Fork 1 1 1 2 1 3 1 4 1 5 local master git checkout -b feature End Work git checkout master 1 6 Feature Branch Pull Requests local feature

37. Your Laptop github.com Feature Branch Merge (Pull Request Accepted) Fork

    Repo (origin) master git fetch upstream git push 1 1 1 2 1 3 1 4 local master Upstream Merge local feature (abandon) Master Repo (upstream) master git diff master upstream/master git merge upstream/master

38. WHEW.

39. GITHUB ISSUES

40. GITHUB WIKIS

41. WEEK FIVE AND BEYOND What else could there be?

42. WHAT ELSE COULD THERE BE? • Harvest - time tracking

    • Jira - story tracking • Testflight - build management • Crashlytics - crash reporting • Trello - information mapping • Dropbox - file sharing • IRC - team chatting • Amazon S3 - cheap storage • Amazon EC2 - dedicated servers

43. QUESTIONS?

44. Good Bye! Nathan Hughes @ndh313