So far, we’ve learned how to work on Git as a single user. Git offers a suite of collaboration tools to make working with others on a project easier. Imagine that you’re a science teacher, develo…

Sally has created the remote repository, science-quizzes in the directory curriculum, which teachers on the school’s shared network have access to. In order to get your own replica of __sci…

Nice work! We have a clone of Sally’s remote on our computer. One thing that Git does behind the scenes when you clone science-quizzes is give the remote address the name origin, so that you …

After you cloned science-quizzes, you had to run off to teach a class. Now that you’re back at your computer, there’s a problem: what if, while you were teaching, Sally changed the __science-qu…

Even though Sally’s new commits have been fetched to your local copy of the Git project, those commits are on the […] branch. Your local […] branch has not been updated yet, so you can’t …

Now that you’ve merged […] into your local […] branch, you’re ready to contribute some work of your own. The workflow for Git collaborations typically follows this order: 1. Fetch and merg…

Now it’s time to share our work with Sally. The command: […] will push your branch up to the remote, […] . From there, Sally can review your branch and merge your work into the […] br…

Congratulations, you now know enough to start collaborating on Git projects! Let’s review. A remote* is a Git repository that lives outside your Git project folder. Remotes can live on the w…