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: version-control.Rmd
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ By the end of the chapter, readers will be able to:
34
34
- Describe what version control is and why data analysis projects can benefit from it
35
35
- Create a remote version control repository on GitHub
36
36
- use Jupyter's Git version control tools for project versioning and collaboration:
37
-
- clone a remote version control repository to a local computer
37
+
- clone a remote version control repository to create a local repository
38
38
- commit changes to a local version control repository
39
39
- push local changes to a remote version control repository
40
40
- pull changes from a remote version control repository to a local version control repository
@@ -128,7 +128,7 @@ Typically when we put a data analysis project under version control,
128
128
we create two copies of the repository (Figure \@ref(fig:vc1-no-changes)).
129
129
One copy we use as our primary workspace where we create, edit, and delete files.
130
130
This copy is commonly referred to as the **local repository**. The local
131
-
copy most commonly exists on our local computer or laptop, but can also exist within
131
+
repository most commonly exists on our computer or laptop, but can also exist within
132
132
a workspace on a server (e.g., JupyterHub).
133
133
The other copy is typically stored in a repository hosting service (e.g., GitHub), where
134
134
we can easily share it with our collaborators.
@@ -265,7 +265,7 @@ committing them to their own local repository, and pushing their commits to the
265
265
to share them with you. When they push their changes, those changes will only initially exist in
266
266
the remote GitHub repository and not in your local repository (Figure \@ref(fig:vc2-changes)).
267
267
268
-
```{r vc6-remote-changes, fig.cap = 'Changes pushed by collaborators, or created directly on GitHub will not be automatically sent to your local computer.', fig.retina = 2}
268
+
```{r vc6-remote-changes, fig.cap = 'Changes pushed by collaborators, or created directly on GitHub will not be automatically sent to your local repository.', fig.retina = 2}
0 commit comments