Skip to content

Latest commit

 

History

History
33 lines (24 loc) · 3.43 KB

info.md

File metadata and controls

33 lines (24 loc) · 3.43 KB

GitHub Tutorial

##Objective

Most Git and GitHub tutorials you’ll find online start with the premise that people want to - or more accurately, the presenter thinks you should - understand the principles and mechanics of version control and what Git is. This tutorial skips all that and assumes that you just want to get working with GitHub with as little difficulty as possible, and that you only want to work with text documents once you’re there - not work with computer code. (A deeper question is why GitHub? I’m not going to argue that GitHub is the way to do text collaboration, or even a good way. In fact, this tutorial is part of a project that will investigate in part whether GitHub is useful for large scale text collaboration and to observe how people use it).

Though you can easily find someone who disagrees with this approach, I believe that - if all you were wanting to do is to learn how to drive - it does not help you right now for me to open up the hood and show you how to check the oil. If, after you have learned how to drive, you want to learn about how a car works, then you will have the context of being able to drive to apply to the mechanisms and principles of how the car works. But our focus today is learning how to get started using GitHub. Once you are collaborating with other people on text documents in GitHub, you can then pull back the layers of the parfait and dig more deeply into working with Git from the command line, understanding the principles of distributed version control and exploring the many facets of GitHub.

##Learning Objectives By the end of this tutorial, you will have:

  1. signed up for a GitHub.com account and set up your account,
  2. created your first project (called a repo or repository) on GitHub.com,
  3. installed and configured Git and GitHub for desktop on you Mac or Windows computer,
  4. cloned a repo from GitHub.com account to your desktop installation,
  5. made changes and saved that repo,
  6. synced your online GitHub.com account with the installation on your computer,
  7. “forked a repo” (that’s what it’s called - “fork a repo”. Go ahead, say it: it’s fun) from someone else on GitHub.com,
  8. submitted that changed repo to the original owner of the file as a suggested modification (this is called “issue a pull request”),
  9. invited a collaborator to help you,
  10. received pull requests from other people,
  11. merged that pull request into a repo you control, and
  12. created your own GitHub page.

The full tutorial is currently available at https://docs.google.com/document/d/17ZZqDhD-Ax4rmfma6Hi26RTREB-ApKZHzht5TBzWdjY/edit?usp=sharing

Moving to this space soon.

Images © 2014 GitHub Inc. All rights reserved. Except as otherwise noted, GitHub Beginners Tutorial for the Next Policy Challenge by Justin Longo is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Permissions beyond the scope of this license may be available at http://policychallenge.asu.edu.