Moving to Git-based Version Control with Small Teams

Moving to Git-based Version Control with Small Teams

Presented on October 20, 2014 at the 2014 HighEdWeb Annual Conference in Portland, OR.

21046df3dd390a36aa6aa0db7264267c?s=128

Waylon Baumgardner

October 20, 2014
Tweet

Transcript

  1. 1.

    Moving to Git-based Version Control with Small Teams Waylon Baumgardner

    Website Manager at California Baptist University ! HighEdWeb Annual Conference - Portland, OR October 20, 2014 @waylonrobert
  2. 10.

    • Riverside, California • Founded in 1950 • 7,900+ students

    • 600+ employees • 150+ majors and concentrations
  3. 22.
  4. 29.
  5. 31.
  6. 32.
  7. 36.
  8. 42.
  9. 48.

    Feature Workflow Data Feature Branch 2 Mikey Feature Branch 1

    Mouth Feature Branch 3 Remote Repository Master Branch
  10. 67.

    • Git is an open-source distributed VCS • Small teams

    = 3 or fewer • 3 Phases for moving to Git: • Plan (hosting, workflow, users, files) • Execute (setup, implement workflow, commit files) • Use (commit, commit, evaluate)
  11. 74.

    What’s a Pull Request? A way to notify team members

    that you have pushed completed code. It’s great for code review. Not part of Git by default. GitHub and Bitbucket have integrated pull requests as a feature.
  12. 78.

    Resources • GitHub: http://github.com • Bitbucket: http://bitbucket.org • Git tutorials:

    • https://www.atlassian.com/git/tutorials/ • http://git-scm.com/about • http://try.github.com • http://gitimmersion.com
  13. 79.

    Key Terms • Repository (repo) = collection of files/branches •

    Local = on your computer • Remote = remotely hosted • Branch = copy of default/master branch • Master branch = default branch created in repo • Commit = action to add files to staging area for pushing • Push = uploading committed files to remote repository