The Ultimate GIT 5-day Challenge

Welcome to Day 1! Today we are going to get setup with an account at GitHub and/or Bitbucket (or both).

As explained in the video, GitHub is one of the most popular places to setup remote repositories, and is where you'll find the bulk of the open-source projects you may want to contribute to. Be clear about one thing, however - Git and GitHub are NOT the same thing!  Our main goals for today are to get an account at one or both of the public websites and then to create our first repository at one or both of these websites.  At the end of the day, we'll have an account and a repository, and will be ready to start working with it soon. Here we go with day 1!

In this video we cover getting an account setup at GitHub

In this lesson we'll create our first repository at GitHub

In this video, we cover getting an account at BitBucket.

In this video, we setup our first repository at BitBucket

Each day we'll just do a "debriefing' that we'll call a reflection on the day. Reflecting is probably the best way to solidify and retain our learning. The reflection is just a quick reminder of what we did and sometimes will include a few other pieces of information to wrap up the day.

This section will get GIT installed on your machine, and get you setup to work with GIT on local repositories

In this lesson we setup GIT for Microsoft Windows machines.

In this video, we get GIT installed on a MAC.  There were a couple of issues that came up but the video shows how to go through the process.  Also, you can follow the instructions here: Get GIT installed

During day 3, we're going to learn how we can go about cloning a repository from a REMOTE location. 

Our repo at GitHub is public, so cloning it will not require any permissions. However, our repo at BitBucket is private, so cloning this repo will require permissions/credentials to be entered.

By the end of day 3, we'll have a LOCAL copy with references set for our REMOTE repositories at GitHub and/or Bitbucket.

In this video, we go over cloning our public repository from GitHub

In this video, we go over cloning a private repository from BitBucket

Day 3 is in the books! We're over half-way through the course! 

Today we took a look at what it takes to clone the repository to our local machine from the remote location. This is critical when we want to setup our machine to start working with repositories that already exist. This also sets up all the tracking references that we will need for our next steps.

Hopefully you got a chance to see what it looks like to clone a public and a private repository, and can now understand the difference as to why cloning would require credentials for a private repository, and a public repository can be freely cloned by anyone.

Welcome To Day 4! Today will be our toughest day, but will also give us the most information for what we want to learn in this course.

In day 4, we're going to make changes on our local file system, ADD them to INDEX, then COMMIT them to the HEAD of our LOCAL repo. Once we've done that, we'll PUSH to the REMOTE repository. As you can see from the emphasis above, we have a few commands and keywords to learn, so let's get started with day 4!

In this video, we are going to do a major activity!  Here, we'll learn what it takes to ADD our changes to the local repository's INDEX.  Then we'll COMMIT the changes to HEAD, and finally, we'll PUSH the changes to our REMOTE repository.

Day 4 was a BIG day for us!

We learned some critical commands today and have essentially learned how the GIT workflow goes from a LOCAL to a REMOTE repository.

We now know how to ADD, COMMIT, and PUSH our changes from LOCAL to REMOTE. 

It's a good idea to get this process down well, so I would recommend that you practice this part of the course a few more times today!

During day 5, we are going to learn what it takes to get changes from the REMOTE repository into our LOCAL repository.  This will become more important as you move into a team of people working on files in the repository, or as you learn about branches in the future. Also, any time you want to just add files or change things at the REMOTE location, you can still just PULL those changes to your LOCAL repository.

Let's get started with day 5!

For our final activity, we're going to simulate one way that we can get changes from the REMOTE repository down to our LOCAL repository.  To do this, we'll use the GIT PULL command.

We DID IT! We made it to the end of the Ultimate GIT 5 day challenge!

Today we went over making changes at the REMOTE repository and pulling those changes down into the LOCAL repository. This is important to keep our local repository in sync with the remote repository.

Hello Everyone! We learned a lot in this course, but we've only scratched the surface with what GIT can do and how to work with GIT outside of a single-person workflow.

In this video, we do a quick reflection on all that we've learned and then go on to talk a bit about things we didn't learn.

Here is the link for my main website, where you can always find the latest information from me:

My Website: http://www.majorguidancesolutions.com 

Follow me on twitter @blgorman
Link up with me on LinkedIn https://www.linkedin.com/in/brianlgorman

I hope you have found our time together valuable and have enjoyed learning the material!

Enjoy!