You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 14-collaboration-using-git.md
+16-14Lines changed: 16 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,26 +67,26 @@ The diagram below shows a typical software development lifecycle with Git
67
67
(in our case starting from making changes in a local branch that "tracks" a remote branch) and the commonly used commands to interact
68
68
with different parts of the Git infrastructure, including:
69
69
70
-
-**working directory** -
70
+
-**working tree** -
71
71
a local directory (including any subdirectories) where your project files live
72
72
and where you are currently working.
73
-
It is also known as the "untracked" area of Git.
74
-
Any changes to files will be marked by Git in the working directory.
75
-
If you make changes to the working directory and do not explicitly tell Git to save them -
73
+
It is also known as the "untracked" area of Git or "working directory".
74
+
Any changes to files will be marked by Git in the working working tree.
75
+
If you make changes to the working working tree and do not explicitly tell Git to save them -
76
76
you will likely lose those changes.
77
77
Using `git add filename` command,
78
-
you tell Git to start tracking changes to file `filename` within your working directory.
78
+
you tell Git to start tracking changes to file `filename` within your working working tree.
79
79
-**staging area (index)** -
80
80
once you tell Git to start tracking changes to files
81
81
(with `git add filename` command),
82
82
Git saves those changes in the staging area on your local machine.
83
83
Each subsequent change to the same file needs to be followed by another `git add filename` command
84
84
to tell Git to update it in the staging area.
85
-
To see what is in your working directory and staging area at any moment
85
+
To see what is in your working working tree and staging area at any moment
86
86
(i.e. what changes is Git tracking),
87
87
run the command `git status`.
88
88
-**local repository** -
89
-
stored within the `.git`directory of your project locally,
89
+
stored within the `.git`working tree of your project locally,
90
90
this is where Git wraps together all your changes from the staging area
91
91
and puts them using the `git commit` command.
92
92
Each commit is a new, permanent snapshot (checkpoint, record) of your project in time,
@@ -106,14 +106,16 @@ with different parts of the Git infrastructure, including:
106
106
is to always do a `git pull` before a `git push`, to ensure you have any latest changes before you push your own.
107
107
108
108
<!--
109
-
Created with https://mermaid.live/edit#pako:eNqVkjFrwzAQhf-KuKmlKd01BAoZ2yUZumi5SmdbRPI58oliQv57JbuloSaFajqd3sd7x-kMlh2BhpFOmXpLO49twmh6Vc4bp6PvW7Xziaxwmh6324eDYFubz4lQq9aLQucW_fVTlb6wxaD2NPDoK77ILcfoZSF-Kyq1p8hCK2zIY7dAK8Ftr4bEdretVgPqOWBH9shZ_stFSi39EXFNfQ0WgrobO05ic4nM6Sd6uYXAH-TU-6Susz3NZvewgVJE9K7s8Fy9DUhHkQzoUjpqMAcxYPpLkWIWPky9BS0p0wby4FC-Vw66wTCWLrma-HX5F_P3uHwCS-vA3Q
109
+
Created with https://mermaid.live/edit#pako:eNqVUsFOwzAM_ZXIJxBldK3aZjlMQsANLhsSEuolNF5brU1KmgjKtH8nbRlsTEPCJ9t5L-9Z9gYyJRAYtPhqUWZ4W_Jc8zqVxMWT0utS5uRRI17O5xdLw_O-vtbIGclLQ7gQI3T_qYfeq4xXZIGNakujdDfCM1XXpRkZvxE9a4G1MnhEa2xbjKQjwGmtFZqsOC21PxsbvBWYrZU1_6DUqHP8w9gB4WuSqiJnbaG0yazzqPSPV1dVlXpDQV46su_oatA5Bw9cUvNSuH1tetkUTIE1psBcKnDFbWVSSOXWQbk1atnJDJjRFj2wjeBmt15gK161rouiN_sw3sBwCh5oZfPiG9Fw-axUffjN3UDb9XLdWxpzjVKgvlFWGmDxdOAD28A7sIhGkygJ_Wjm08APp4EHHbAknszCJAoCSumUhvHWg49Bz5_QJPJdRGEYz5IkpttPWWLlPg
0 commit comments