Git Basics

available on each local copy, so you could do a lot of operation without internet connection.
If central copy of data will be lost, any local copy could be used to restore central.
Lightweight branching.
Possibility of working with several remotes in one time.
Storing only current copy of data in a local repository could be an advantage.
Easier workflow for novice users.

Advantages of distributed VCS

Advantages of centralized VCS

snapshots

Debian-based distribution like Ubuntu, try:
$ sudo apt-get install git-all
Just go to the next link and the download will start automatically. 
http://git-scm.com/download/win
To find more ways to download and install git visit:
https://git-scm.com/downloads

Linux

Windows

Other

for all system users)
--global (Saves configuration for current system user)
git config --global user.name “Ivan Ivanov" (To set user name)
git config --global user.email ivan_ivanov@epam.com (To set user email)
Setup Notepad++ as core editor
git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
git config --list (To get current configuration)
git help
git --help
man git-

git config

git help

for all system users)
--global (Saves configuration for current system user)
git config --global user.name “Ivan Ivanov" (To set user name)
git config --global user.email ivan_ivanov@epam.com (To set user email)
Setup Notepad++ as core editor
git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
git config --list (To get current configuration)
git help
git --help
man git-

git config

git help

of your repository. All files, which are match patterns from gitignore, would be untracked by default. This could be binary files; files, which are generated by IDE, logs, ect. So all of this files exist in you project directory, but you will never want to commit them to repository.
The rules for the patterns you can put in the .gitignore file are as follows:
Blank lines or lines starting with # are ignored.
Standard glob patterns work.
You can start patterns with a forward slash (/) to avoid recursivity.
You can end patterns with a forward slash (/) to specify a directory.
You can negate a pattern by starting it with an exclamation point (!).

# no .a files
*.a
# but do track lib.a, even though you're ignoring .a files above
!lib.a
# ignore all files in the build/ directory
build/
# ignore all .pdf files in the doc/ directory
doc/**/*.pdf

file but have not committed it to your local database
Staged: you have marked a modified file in its current version to go into your next commit snapshot.
Committed:  the data is safely stored in your local database.
This leads us to the three main sections of a GIT project:

project under version control. Command should be executed in the root project directory. Pay attention! After invoking this command you files will be untracked. You should track them and do initial commit manually.
git clone [url]
This command is used to clone remote repository and create local copy for you. After cloning repository all files are in unmodified state.
For cloning repository you could use different transfer protocols. For example: https, ssh.

Initialization

Clone

out in which states you repository files are.

Status

Lifecycle

proposes. Two of them are:

On branch master
Untracked files:
(use "git add ..." to include in what will be committed)
README
nothing added to commit but untracked files present (use "git add" to track)

Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: CONTRIBUTING.md
Prepare modified files for commit. [modified -> staged]
Put untracked file under VCS, prepare them for commit. [untracked -> staged]

CONTRIBUTING.md
we will get the next result:

$ git status
On branch master
Changes to be committed:
(use "git reset HEAD ..." to unstage)
new file: README
modified: CONTRIBUTING.md

file?

vim CONTRIBUTING.md
$ git status
On branch master
Changes to be committed:
(use "git reset HEAD ..." to unstage)
new file: README
modified: CONTRIBUTING.md
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: CONTRIBUTING.md

Git stages a file exactly as it is when you run the git add command.

changes.

$ git commit -m "Story 2: Extending readme files"
[master 463dc4f] Story 2: Extending readme files
2 files changed, 2 insertions(+)
create mode 100644 README

You could also use
git commit –a
to skip staging area.

which should be deleted.

$ rm PROJECTS.md
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
(use "git add/rm ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
deleted: PROJECTS.md
no changes added to commit (use "git add" and/or "git commit -a")

rm 'PROJECTS.md'
$ git status
On branch master
Changes to be committed:
(use "git reset HEAD <file>..." to unstage)
deleted: PROJECTS.md

README.md README
$ git status
On branch master
Changes to be committed:
(use "git reset HEAD ..." to unstage)
renamed: README.md -> README

shows SHA-1, commit name, author, email, date.
Some of the most popular options:

$ git log --pretty=oneline -1
ca82a6dff817ec66f44342007202690a93763949 changed the version number
$ git log --pretty=format:"%h - %an, %ar : %s“ -1
ca82a6d - Scott Chacon, 6 years ago : changed the version number

some changes in your last commit.

$ git status
On branch master
Changes to be committed:
(use "git reset HEAD ..." to unstage)
renamed: README.md -> README
modified: CONTRIBUTING.md

git reset HEAD [file]

To unstaging a staged file. Git status will help you:

Unmodifying a modified file. Git status will help you again:

git checkout --[file]

Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: CONTRIBUTING.md

to one of commits.

What branch is?

Creating new branch

git branch [name]

HEAD a special pointer, which allows GIT to know what branch you’re currently on.

Only creates a branch, does not switch on it.

a change'

Switch to another branch

git checkout master

[made another changes]
git commit -a -m 'made other changes'

to a new branch 'iss53'

[working on iss53]
$ git commit -a -m ‘issue53 add footer'

$ git checkout master
Switched to branch 'master'

$ git checkout -b hotfix
Switched to a new branch 'hotfix‘
[do some fixes]
$ git commit -a -m 'fix something'

$ git checkout master
$ git merge hotfix
Updating f42c576..3a0874c
Fast-forward

git merge

 Join two or more development histories together

$ git branch -d hotfix
Deleted branch hotfix (was 3a0874c).
$ git checkout iss53
Switched to branch 'iss53'
[Finish working on iss53]
$ git commit -a -m 'finish [issue 53]'

Merge made by the 'recursive' strategy.

in index.html
Automatic merge failed; fix conflicts and then commit the result.

Git hasn’t automatically created a new merge commit. It has paused the process while you resolve the conflict. If you want to see which files are unmerged at any point after a merge conflict, you can run git status:

$ git status
On branch master
You have unmerged paths.
(fix conflicts and run "git commit")
Unmerged paths:
(use "git add ..." to mark resolution) both modified: index.html
no changes added to commit (use "git add" and/or "git commit -a")

git mergetool

Run an appropriate visual merge tool

After merging you should add to index and commit the changes.

serverfix
...
* [new branch] serverfix -> serverfix

git push origin serverfix:newname

to give remote branch another name

Deleting remote branch

git push [remotename] :[branch]

Fetching / pulling remote branches

$ git fetch origin
...
* [new branch] serverfix -> origin/serverfix

Someone else do:

Local branch is not created.

$ git checkout -b serverfix origin/serverfix

to get a local copy of remote branch

commit: n3
2ae10cd HEAD@{12}: commit: n2
c1c51a3 HEAD@{13}: commit: n1
ad0096f HEAD@{14}: checkout: moving from master to new
ad0096f HEAD@{15}: commit: clean

get reference log