Today, GIT is pretty much the de facto standard
for co-repository.
In this example, we're going to walk through
how to set up a local repository
using GIT and just go over a few commands
just to get familiar with it.
We're not going to go very in depth,
just a little surface level information
about how to commit changes, what commit changes are,
how to add culture, repository, et cetera.
Disable repo option is going to be used again
to make sure that we're not using that
for our default search.
We want to disable it so it'll use the internet.
Okay, that was successful.
Next, we're going to use the GIT configure command
just to make some global configuration changes.
So this is our name and our email address.
We GIT config.
Global.
The same thing, but we're going to change the email address.
All right.
Now, I'm going to make a directory.
This is where we're going to commit all of our changes
and store all of the code that we plan
on using for GIT, I'm going to make a directory.
This, we'll call it "Dell Project".
Okay, now let's initialize this folder.
So we used a GIT config command to set up the folder
for all the information that we're going to be receiving,
and it configures the folder to respond to GIT commands
and everything that needs to be done
GIT will handle it for us in that directory.
So if we looked at that directory,
we'll see we have a few new files in there,
like the GIT directory.
We'll see it again,
as all the necessary configuration files
that's required to have GIT up and running.
All right, so now we're going to actually create
and manage a project but we're just going to use
a simple text file,
and we use the tried-and-true Hello World.
So we'll do dev-project,
Hello World,
All right.
And type in Hello World.
From Jamario Kelly,
all right, right click.
Next, we're going to cd into that dev project.
Okay, and now we're going to run the GIT status command.
All right, so I see it's looking through the folder
and it has identified the HelloWorld.txt file
that we just created, but it's not being tracked
because we have to use an Add command to let GIT know,
Hey, this file?
I want you to manage and track.
So let's do that first.
Okay, now we're going to do the GIT commit
to actually save the information.
Now this dash M option is just the message
that we want to include.
We can call it our initial commit.
Okay, see, they went through successfully.
Now, let's check the status.
All right, we see it's letting us know
there's nothing to commit, the working director is clean,
meaning that per the last commit we did,
any changes that was added are now saved.
Now we're going to change this file one more time.
Okay, let's make one more change to this.
Let's see, GIT version
control test, okay.
Let's do GIT status, see what it says to us now.
Now you see that since the Hello World txt
is being managed by GIT,
It's been identified as being modified.
But again, in order to update to the next commit
we still need to add this txt.
Okay, So we're going to do GIT add Hello World.
Go ahead and commit this,
I'm going to add our message,
call it revision one.
Okay.
I want to go to GIT status.
Shouldn't be anything that's pending.
All right.
Final command's going to run is the GIT log.
What I get is a clean view
of all the changes that's been made.
Now, this would be useful when you want to revert
to a previous version, you can use the commit identifier
that's located to the right of the commit key.
We're not going to go over that in this lesson,
it can get pretty in depth when it comes to GIT,
but those are the basics
just to understand a little bit about GIT,
how to set up a repository,
and to view some of the changes
and how GIT manages those changes.
Thank you for sticking with this walkthrough,
and I'll see you in the next lesson.