@@ -49,6 +49,15 @@ the same. We are currently working on producing new Python-based images and exam
49
49
for this chapter.
50
50
```
51
51
52
+ ``` {note}
53
+ This book was originally written for the R programming language, and
54
+ has been edited to focus instead on Python. This chapter on version control
55
+ has not yet been fully updated to focus on Python; it has images and examples from
56
+ the R version of the book. But the concepts related to version control are generally
57
+ the same. We are currently working on producing new Python-based images and examples
58
+ for this chapter.
59
+ ```
60
+
52
61
## Chapter learning objectives
53
62
54
63
By the end of the chapter, readers will be able to do the following:
@@ -284,7 +293,6 @@ Committing the modified files in the staging area to the local repository histor
284
293
```
285
294
286
295
287
-
288
296
### Pushing changes to a remote repository
289
297
290
298
``` {index} git;push
@@ -306,7 +314,6 @@ name: vc5-push
306
314
Pushing the commit to send the changes to the remote repository on GitHub.
307
315
```
308
316
309
-
310
317
### Pulling changes from a remote repository
311
318
312
319
If you are working on a project with collaborators, they will also be making changes to files
@@ -776,7 +783,7 @@ and click on the blue "Commit" button ({numref}`git-commit-01`).
776
783
It is highly recommended to write useful and meaningful messages about what
777
784
was changed. These commit messages, and the datetime stamp for a given
778
785
commit, are the primary means to navigate through the project's history in the
779
- event that you need to view or retrieve a past version of a file, or
786
+ event that you need to view or retrieve a past version of a file, or
780
787
revert your project to an earlier state.
781
788
When you click the "Commit" button for the first time, you will be prompted to
782
789
enter your name and email. This only needs to be done once for each machine
0 commit comments