Literature review contents comleted

Author: Alireza Khodabakhsh

README.md

@@ -71,25 +71,112 @@ touch index.py
 
 
 # Literature review
-- [Working tree](#)
-- [Commit](#)
-- [Stage](#)
-- [Tracked/Untracked file](#)
-- [Modifed file](#)
-- [Nothing added to commit](#)
-- [Changes not staged for commit](#)
-- [HEAD](#)
-- [Local](#)
-- [Origin](#)
-- [Remote](#)
-- [Both modified](#)
-- [Clone](#)
-- [Ahead of origin/master](#)
-- [Behind of origin/master](#)
-- [Your branch is up to date](#)
-- [Origin/master & master](#)
-
-
+- [Working tree](#working-tree)
+- [Commit](#commit)
+- [Stage](#stage)
+- [Tracked/Untracked file](#trackeduntracked-file)
+- [Modifed file](#modifed-file)
+- [Nothing added to commit](#nothing-added-to-commit)
+- [Changes not staged for commit](#changes-not-staged-for-commit)
+- [HEAD](#head)
+- [Local](#local)
+- [Origin](#origin)
+- [Remote](#remote)
+- [Both modified](#both-modified)
+- [Clone](#clone)
+- [Ahead of origin/master](#ahead-of-originmaster)
+- [Behind of origin/master](#behind-of-originmaster)
+- [Your branch is up to date](#your-branch-is-up-to-date)
+- [Origin/master & master](#originmaster--master)
+- [Tag](#tag)
+
+
+## Working tree
+* The working tree, or working directory, consists of files that 
+you are currently working on. 
+* You can think of a working tree as a file system where you can
+view and modify files.
+
+## Commit
+* save your file/files that put in stage, and after commit, 
+git consider this file/files as a HEAD file. You will be 
+availble call every commit in future.
+* Git considers each commit change point or "save point". 
+It is a point in the project you can go back to if you find 
+a bug, or want to make a change.
+
+## Stage
+* stage is a place that, 1. untracked files put in stage in 
+order to in commit phase, tracked by git. or 2. 
+modified/deleted/... files that already tracked by git, 
+put in stage in order to save changed in commit phase.
+
+## Tracked/Untracked file
+* you have NEW file/files that if contents modified, git can't 
+sense alterations.
+* Untracked basically means that Git sees a file you didn't have 
+in the previous snapshot (commit), and which hasn't yet been 
+staged.
+* Untracked files are most of the time files you don't want to
+be controlled, because for example they are generated by your 
+compiler.
+* Tracked - files that Git knows about and are added to the 
+local repository.
+* Untracked - files that are in your working directory, but 
+not added to the local repository.
+
+## Modifed file
+* git always check tracked file/files,when file/files contents has 
+been changed, git label it/these to modified file.
+
+## Nothing added to commit
+* no file/files are in stage to commit.
+
+## Changes not staged for commit
+* your tracked file/files has been modified, and NOT yet put in 
+stage to commit.
+
+## HEAD
+* HEAD is last/final commit (last saved alterations).
+
+## Local
+* local meaning is in your personal computer.
+* EX: 
+local commit : a written commit that has been write in your computer and has not yet push in remote repository.
+
+## Origin
+* origin" is the name of the remote repository where you want to 
+publish you commits. By convention, the default remote repository 
+is called "origin", but you can work with several remotes 
+(with different names) as the same time. More information here.
+## Remote
+* A remote repository in Git, also called a remote, is a Git 
+repository that's hosted on the Internet or another network.
+## Both modified
+* recommend you : commit and merege early early!
+* recomend you : pull repository, and edited it and commit and 
+push it.
+## Clone
+* duplicate and download everything of remote repository
+when you use command clone in git, git create new folder with 
+name as same as name of remote repo in github and copy and 
+download everything and put it them on this folder.
+## Ahead of origin/master
+
+## Behind of origin/master
+* when you fetch remote repo on your local repo, this guide say 
+you, remote repo have new commits so that you have not these 
+commits in your local repository. and you "behind of 
+origin/master" this meaning that, you are NOT update rather to 
+origin remote on master branch.
+## Your branch is up to date
+* when pull (fetch and merge) remote branch with your local branch
+this guide showed.
+## Origin/master & master
+* "remote name"/"remote branch name" & "local branch name"
+## Tag
+* Git has the ability to tag specific points in a repository’s 
+history as being important.