Congrats on being selected as a fellow! Here's the practical Git lesson I wrote for the Fall 2017 semester. It was requested I make it repeatable for future semesters, so here we are. I'm comfortable maintaining this as long as GitHub is around (if you're reading this after that point...sorry ¯\_(ツ)_/¯).
If there's something in the README that you or your class found confusing, please PR changes back into THIS repo (not your forked one) so that future semesters have the new version of the README.
If you'd like to add new questions to the project, you can do that too, just be mindful that it should be easy enough that students can finish it in a reasonable time in class. Also please add stubs and tests for all 3 languages, not just your favorite language.
In order to use this for your class, just:
- Fork the repo!
- Remove this section from the README
- Send YOUR link out to your students 1-2 days before class asking them to complete the tasks in the setup section
- In class, have them walk through the steps below to answer a practice interview question, and that's it!!
Welcome to Practical Git! Today we're going to practice working using git and GitHub the way they're used in the real world. My instructions will assume you're using the command line (using an app like Terminal or iTerm). You can also use a git GUI like SourceTree or GitHub Desktop, though you may have to search the Internet for instructions on how to use those.
Instructions that involve a command-line tool will look like this:
$ git-command --argument
the outputBefore we start the tutorial, please make sure you've done the following things:
- Create a GitHub account
- Install git (open a command line window and type
git, if you see a list of available commands you already have git installed) - Set up your account locally
We'll walk through this in class, you do not need to do this before class.
For this exercise, you're going to do something called "forking" a repository. On co-op you'll be a member of a repository and you'll work off of something called a "branch," but for open-source projects this will be the actual workflow. A fork is a copy of the repository that you own and can work on freely without affecting the original code.
On the top right corner of the page there should be a button that says "Fork," you can click that and you're done!
Cloning a repository is the process of downloading the code to your machine. This creates a local copy that is linked to the version hosted on GitHub. To do this, in a directory dedicated to code you can run:
$ git clone https://github.com/MY_USERNAME/practical-git.git
Cloning into 'practical-git'...
remote: Counting objects: 19, done.
remote: Total 19 (delta 0), reused 0 (delta 0), pack-reused 19
Unpacking objects: 100% (19/19), done.
NOTE: If you used SSH keys to set up git instead of HTTPS that url will become git@github.com:MY_USERNAME/practical-git.git.
Once you've got the code on your machine, you'll see a few language-specific folders. Each folder contains the same questions, so just choose your favorite language and open that folder in your IDE/Editor of choice!
Go ahead and code out the solution to the problem, maybe even write some tests to prove it works :)
Now we're going to create what's called a "commit." A commit is a small chunk of code that represents a complete piece of work. Normally you'd commit any time you reach a stopping point, but for simplicity's sake we'll just commit once you're done writing code.
An important part of a commit is the "commit message," you need to write a descriptive message telling everyone else what code is in your commit. A bad message would be something like some changes, a good message would be something like implemented and wrote tests for python palindrome problem.
To create a new commit, we need to tell git which files we want to add, create the commit itself, and then "push" it up to GitHub:
$ git add . # adds all files in the current directory. you could put an
# individual file path if you only want to commit a specific file
$ git commit -m "YOUR MESSAGE HERE"
[master 12345678] YOUR MESSAGE HERE
2 files changed, 58 insertions(+)
$ git push origin master
Counting objects: 4, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 826 bytes | 826.00 KiB/s, done.
Total 4 (delta 1), reused 0 (delta 0)
remote: Resolving deltas: 100% (1/1), completed with 1 local object.
To github.com:MY_USERNAME/practical-git
8a5b2fd..29d9916 master -> masterIn order to actually get your code back into the original project, you have to submit what's called a "Pull Request," a request for the project owner to "pull" the changes you've made on your fork back into the original project. To do this, navigate to the GitHub page for your fork (should be https://github.com/YOUR_USERNAME/practical-git).
At the top you should see a yellow bar prompting you to create a pull request, click on the "Compare and Pull Request" button.
On the next page, put in a title, a brief description of your changes (in this case, your solution), and click "Create Pull Request"!
On co-op you'll be doing this yourself once someone else reviews your code, but in open source projects the project owner is in charge of merging. In fact, you likely will not even have permissions to merge the PR unless you've been added as a contributor.
In this stage you may have to resolve "merge conflicts," when two people modify the same code and git can't tell Whose Code Is It Anyway. We can walk through this in person as it's a little complex to cover in this README.