Git中經常使用術語

Key Terms

版本控制系統（VCS）或源代碼管理器（SCM）：一個VCS容許您：將文件恢復到之前的狀態，將整個項目恢復到之前的狀態，回顧隨時間變化的變化，看誰最後修改了可能引發的事情。一個問題，誰提出了一個問題，何時，等等。

Version Control System (VCS) or Source Code Manager (SCM): A VCS allows you to:
revert files back to a previous state, revert the entire project back to a previous state,
review changes made over time, see who last modified something that might be causing
a problem, who introduced an issue and when, and more.

提交（快照）：Git認爲它的數據就像一組迷你文件系統的快照。每次提交或保存您的項目在Git中的狀態時，基本上都須要圖片的全部文件看起來像在那一刻，並存儲一個參考快照。
Commit (snapshot): Git thinks of its data like a set of snapshots of a mini file system.
Every time you commit, or save the state of your project in Git, it basically takes a
picture of what all your files look like at that moment and stores a reference to that
snapshot.

存儲庫（RePo）：包含項目工做的目錄，以及一些文件（默認在Mac OS X中隱藏），用於與Git通訊。倉庫能夠在計算機上本地存在，也能夠做爲另外一臺計算機上的遠程副本存在。
Repository (repo): A directory that contains your project work, as well as a few files
(hidden by default in Mac OS X) which are used to communicate with Git. Repositories
can exist either locally on your computer or as a remote copy on another computer.

工做目錄：您在計算機的文件系統中看到的文件。當你在代碼編輯器上打開項目文件，您正在使用工做中的文件目錄。這與已保存的文件造成對比（在提交中）！在存儲庫中。在使用Git時,工做目錄也不一樣於命令行。當前工做目錄的概念，它是您的shell的目錄
Working Directory: The files that you see in your computer's file system. When you open your project files up on a code editor, you're working with files in the Working Directory. This is in contrast to the files that have been saved (in commits!) in the repository. When working with Git, the Working Directory is also different from the command line's concept of the current working directory which is the directory that your shell is "looking at" right now.

簽出：當存儲庫中的內容被複制到工做目錄時。它能夠從存儲庫中籤出許多東西；文件、提交、分支等。分級區域或分級索引或索引：存儲在GIT目錄中的文件有關下一次提交的內容的信息。你能夠想到舞臺做爲準備表，Git將採起下一個提交。分級索引的文件是準備添加到存儲庫中。

Checkout: When content in the repository has been copied to the Working Directory. It is possible to checkout many things from a repository; a file, a commit, a branch, etc. Staging Area or Staging Index or Index: A file in the Git directory that stores information about what will go into your next commit. You can think of the staging area as a prep table where Git will take the next commit. Files on the Staging Index are poised to be added to the repository.

Sa*：SHA基本上是每一個提交的ID號。它是一個40字符串。由字符（0—9和a- f）組成，並根據文件的內容Git中的目錄結構。「沙」是「沙哈」的速記。沙沙多是這樣的：E2ADF8AE3E2E4ED40ADC75 CCF99D0A869AFEB6

SHA: A SHA is basically an ID number for each commit. It is a 40-character string composed of characters (0–9 and a–f) and calculated based on the contents of a file or directory structure in Git. "SHA" is shorthand for "SHA hash". A SHA might look like this:
e2adf8ae3e2e4ed40add75cc44cf9d0a869afeb6

分支：當一條新的發展線偏離發展主線。這種替代的發展路線能夠繼續下去。改變主線。回到遊戲中保存點的例子，你能夠想到一個分支你在遊戲中作一個保存點，而後決定嘗試一個冒險的動做。遊戲。若是冒險行動沒有成功，那麼你能夠回到保存點。這個使分支很是強大的關鍵是你能夠保存保存點。一個分支，而後切換到另外一個分支，並在那裏保存保存點。

Branch: A branch is when a new line of development is created that diverges from the
main line of development. This alternative line of development can continue without
altering the main line.

Going back to the example of save point in a game, you can think of a branch as whereyou make a save point in your game and then decide to try out a risky move in thegame. If the risky move doesn't pan out, then you can just go back to the save point. Thekey thing that makes branches incredibly powerful is that you can make save points onone branch, and then switch to a different branch and make save points there, too.