.git<\/code>.). It includes all the files and sub-directories in that directory.<\/li>\n- commit<\/strong>\u00a0\u2014 A\u00a0commit<\/strong>\u00a0is a snapshot of your working tree at some point in time. The state of HEAD (see below) at the time your commit is made becomes that commit\u2019s parent. This is what creates the notion of a \u201crevision history\u201d.<\/li>\n
- branch<\/strong>\u00a0\u2014 A\u00a0branch<\/strong>\u00a0is just a name for a commit (and much more will be said about commits in a moment), also called a reference. It\u2019s the parentage of a commit which defines its history, and thus the typical notion of a \u201cbranch of development\u201d.<\/li>\n
- tag<\/strong>\u00a0<\/a>\u2014 A\u00a0tag<\/strong>\u00a0is also a name for a commit, similar to a\u00a0branch<\/em>, except that it always names the same commit, and can have its own description text.<\/li>\n
- master<\/strong>\u00a0\u2014 The mainline of development in most repositories is done on a branch called \u201c**master**\u201d. Although this is a typical default, it is in no way special.<\/li>\n
- HEAD<\/strong>\u00a0\u2014\u00a0HEAD<\/strong>\u00a0is used by your repository to define what is currently checked out:\n
\n- If you checkout a branch, HEAD symbolically refers to that branch, indicating that the branch name should be updated after the next commit operation.<\/li>\n
- If you checkout a specific commit, HEAD refers to that commit only. This is referred to as a detached\u00a0HEAD<\/em>, and occurs, for example, if you check out a tag name.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
The usual flow of events is this: After creating a repository, your work is done in the working tree. Once your work reaches a significant point \u2014 the completion of a bug, the end of the working day, a moment when everything compiles \u2014 you add your changes successively to the index. Once the index contains everything you intend to commit, you record its content in the repository. Here\u2019s a simple diagram that shows a typical project\u2019s life-cycle<\/a>:<\/p>\n![\"Project](\"https:\/\/www.booksofall.com\/es\/wp-content\/uploads\/sites\/5\/2023\/05\/lifecycle.png\")
<\/p>\n
With this basic picture in mind, the following sections shall attempt to describe how each of these different entities is important to the operation of Git.<\/p>\n","protected":false},"excerpt":{"rendered":"