GIT
Version Control System
- GIT is a version control system
- Its basically means that GIT is a content
tracker
- The purposes of GIT is to manage a project,
or a set of files, as they change over time
- Version control is a piece of software that
helps teams or individuals manage their
source code over time
- It tracks changes in a project so that if
something breaks while you are working on
it or any updates made
- You can compare the difference between the
current project and a previous version of the
project
- History of GIT
a. Linus Torvalds the developer of Linux,
designed GIT in 2005
b. This led Linus Torvalds to develop their
own tool based on some of the lessons
they learned while using BitKeeper. This
tool was GIT
c. The in – joke was that I name all my
projects after myself, and this one was
named GIT
d. GIT is british slang for ‘stupid person’
words by Torvalds
e. There’s a made – up acronym for it,
Global Information Tracker, but that’s
really a ‘backronym’
GitHub
- GIT needs a place to host the repository or -
workplace for everyone. Here, GitHub comes
into the picure
- There are two ways you can host your
repositories
1. Online
That is on the cloud
2. Offline
That is self – installed on your server
- GitHub owned by Microsoft
- GitHub is a Git repository hosting service
- It hosts the service for everyone like you host
a party
- It provides a web – based graphical interface
- It helps every team member to work together
from anywhere and makes it easy for them to
collaborate
Why GIT ?
- Real life projects generally have multiple developers
working in parallel
- Just like the script writers team
- So they need a version control system like GIT to
make sure that there are no code conflicts between
them
- It allows you to have track of all the changes by
different contributors to your project
- Repository
a. A repository is just a file location where you are
storing all the files related to your project
b. In our case a repository will contain code – based
files
c. A repository in GIT could be considered similar to
your project folder
d. GIT could track all the changes happening inside
the folder
- Track changes
a. When previous people collaborate on a project
b. It’s hard to keep track of revisions, like who
changed what, when, and where those files are
stored
c. GitHub takes care of this problem by keeping
track of all the changes that have been pushed to
the repository
- In GIT there’s a little ‘undo’ command for almost
every situation, it makes working more easy
- Working in GIT saves a lot of time
- Tracking any changes made or any other update
becomes very simple with GIT
Installation
GitHub is very easy to install and simple to work
with. Installing GitHub on your operating systems:
a. Open a browser
b. Visit https://desktop.github.com/
c. Click download for Windows (64bit)
d. When prompted, click Run
e. Allow the installation to download and install
- GitHub helps all the team members to stay
on the same page and stay organized
- Why GitHub ?
a. GitHub allows you to keep both local and
remote copies of your project
b. Now you know that, GitGub allows you
to keep both local dan remote copies of
your project
c. A project that you can publish it among
your team members as they can use it and
update it from there itself
d. The GitHub repository is so large that it -
has 25 million users, which is actually
more than the population of some country
e. It is the world’s largest software
development platform
f. Putting your project to a shared, public
repository makes it instantly discoverable
for those 25M users.
g. You can easily discover code written by
others, learn from it, and even use it for
your own projects.
h. Version control on GitHuv are very
similar to MS office or Google drive. It
tracks all the changes or updates made to
your project and who makes them.
Lets get started
- Important terminologies - How it works (1) – local to remote repository
a. GIT Bash – is a command – line prompt
for windows. It allows user to type GIT
commands that make souce code
management easier through versioning
Repository
a. Is a virtual storage of your project, it allows you to
save versions of your code, which you can access
when needed
b. To create a new repo, we will use the git init
command
c. Git init is a one – time command you use during
the initial setup of a new repository. Executing
this command will create a new .git in your
directory
- Cloning
a. The git clone command can makes a local copy of
the repository and create a working directory
b. You got your virtual storage or repository ready
and you know how it’s done
c. What if you want the same repository on your
local computer ?
d. Repository can be cloned just like the youtube
video you can download to watch it when you are
offline
e. Step
1. To clone a repository, go to the repository
page which you want to clone
2. Press clone or download button
3. Copy the code or URL that appears after
pressing the button
4. Press the following command to clone the
repository :
git clone <URL>
5. It would take a few seconds to clone the
repository onto your system, and the cloning is
done
How things work
a. If you’re the only person working on your project,
chances are you’ll never need to set up a remote
repository. What if you want to share data with
your teammates ? Local repositories reside on the
 and commit history
b. The Working Tree – the name itself tells
what it means. Working Tree is the area
where you are currently working. It is
where your files live. This area is also
known as the “untracked” area of git
c. Command – one thing you should keep in
mind is that the changes will not be saved
until you explicitly save them. Any
changes to files will be updated and seen
in the working tree. To see what is in
your woking tree run the command : git
status. This command will show you two
things :
1. The files in your working tree
2. The files in your staging area
d. Staging area – the man hired by the script
writers team for keeping the records of
updates and changes made. One day one
of script writer made some changes in the
script or updated the script. So now any
of the script writer wants to specifically
see the changed part of the script ?
The staging are comes in picture, when
Git starts tracking and saving changes
that occur in files. You tell git that I want
to track these specific files, then Git
moves them from your Working tree to
the staging area
e. Commit – On GitHub, saved changes are
called commits. Each commit has an
associated commit message. It is a
description explaining why a particular
change was made. Commit messages
capture the history of your changes, so
other contributors can understand what
you’ve done and why
I guess you are aware of the word -
commit. The ‘commit’ command is
basically used to save your changes to the
local repository. They are the core
building block units of a Git project
timeline
You can think of Commits as snapshots
or milestones along the timeline of your
Git project. They are created with the git
commit command to capture the state of
a project at that point in time. You should
know that Git snapshots are always
computers of team members
b. Remote repository comes in the rescue
c. A remote repository in Git is a common repository
that all team members use to exchange their
changes
d. Every member can access the repository and make
changes which everyone can access
e. In most cases, such a remote repository is stored
on a code hosting service like GitHub or on an
internal server
f. We have been working only in the local
repository. Each developer will work in their local
repository but eventually, they will push the code
into a remote repository. Once the code is in the
remote repository, other developers can see and
modify that code
g. let’s create a new repository in GitHub and
convert the repository from local repository to
remote repository
h. step
1. Step 1 : after creating a repository on GitHub,
you will get a URL for your repository. Copy
that URL
2. Step 2 : now to point your local repository to
the remote repository, use the following
command
git remote add origin [repository url]
3. Step 3 : in order to push all the code from the
local repository into the remote repository, use
the following command :
git push -u origin master
note* this pushes the code from the master
branch in the local repository to the master
branch in the remote repository
How it works (2) – branching
a. What if Rob made some changes in the script and
the next day Sam erased those changes to make
his new update. This is going to be a big cause of
anger for Rob when he gets to know. How are
they gonna solve this problem ?
b. Branching is the practice of creating copies of
programs or objects to work in parallel versions,
retaining the original and working on the branch
or making different changes to each
c. For example, you’re going to have a bunch of
different features or ideas in progress at any given
time – some of which are ready to go, and others
 committed to the local repository
Commit commands :
There are two important commit
commands
1) git add
Used to save a copy of the current
state of the project you make changes
with git add
2) git commit
After you’re satisfied with he made
snapshot, you commit it to the project
history with git commit
Set up Notepad++ for Git Bash in Windows
- why notepad++
1. Notepad++ is a very simple and easy to
which are not. Branching exists to help you
manage this workflow
i. When you create a branch in your project, you’re
creating an environment where you can try out
new ideas. Changes you make on a branch don’t
affect the main branch, so you’re free to
experiment and commit changes
j. This is also useful when we have multiple people
working on a project. Each person creates a
branch for the feature or bug – fix they are
working on and when they are finished they merge
it back into the master branch
k. Step (new Git branch)
1. Step 1 : create a new branch with this
following command
git branch [branch-name]
Note* : now we created a new branch called
“test-branch”
2. Step 2 : confirm that we have created a new
branch
git branch
test-branch
* master
Note* : we can see the new branch with the
name “test-branch”, but the * beside master
specifies that we are currently on that branch
3. Step 3 : checkout from a branch. Checkout is
the command used to check out a branch.
Moving us from the current branch, to the one
specified at the end of the command :
git checkout test-branch
Switched to branch ‘test-branch’
Note* : now we have moved our current
workspace from the master branch, to the new
branch. open your favourite editor and make
some changes
4. s
it remote add origin [repository url]
https://www.w3schools.com/git/git_branch.asp
 use text editor and used by a good
number of developers in the community
2. There are loads of plugins available for
Notepad++ which can make your tasks
simple
3. Notepad++ which can make your tasks
simple. With the support of many
programming languages to code in,
Notepad++ is very fast while starting up.

- Step
1. Prerequisite : Notepad++ should be
installed on your system. You can
download the same from here. Remember
the directory in which you have installed
the Notepad (notepad++.exe)

https://www.toolsqa.com/git/set-up-
notepad-for-git-bash/ (checkpoint)
2.