Basic Git Workflow for Team/OpenSource Projects on GitHub

Review some of the basics when it comes to working with Git and GitHub in a team setting, where you have to worry about changes other developers may have made to the same project. This is a quick and dirty video just to review the process and common issue you may run into when working on a project with multiple other people.

We will cover:
0:00 - An introduction to this video's purpose
0:50 - Access the repo on github
3:20 - Forking the repo to our own personal account for quicker access
4:59 - Cloning the repo onto our local machine
8:07 - Adding changes to the project
11:10 - Stashing those changes (in case you forget to create a new branch first)
12:26 - Creating a new branch
17:19 - Stash pop to get changes from master back on to the right branch
17:48 - Staging and committing changes we make
19:13 - Pushing changes up to github
19:57 - Reviewing Git pull
21:02 - Using Git pull
21:48 - Using Git push
22:27 - Opening github to confirm the branch was added successfully
24:25 - Submitting pull requests to our project (on the user's github account)
27:28 - Submitting pull requests (from the user's github account), up to the original project i.e. contributing
28:59 - Reviewing (others') changes / pull requests
32:20 - Syncing the user account repo with the original project i.e. syncing forks
33:03 - Keeping new changes up-to-date on local machine
33:32 - Deleting the branch from our local machine to prevent wasted space
34:00 - using git pull to update master branch
35:27 - Summary of what has been covered
36:42 - What causes, and how to handle, merge conflicts
39:56 - Review of Key Points and Takeaways
42:57 - Ways to customize and improve your workflow going forward