From f5058df84eda2c7fbd8fc047079d3e9e955e3411 Mon Sep 17 00:00:00 2001 From: yaoyahan <1737469763@qq.com> Date: Tue, 8 Sep 2026 16:07:51 +0800 Subject: [PATCH 1/3] docs: update README --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 3a87181..93b2d2a 100644 --- a/README.md +++ b/README.md @@ -110,3 +110,5 @@ An important principle of version control is that you **never** duplicate files. Great job! If you comfortably navigated these exercises, then you have the necessary basics for working with git and GitHub. These will get you most of the way through the course, and indeed, through your programming career. The most important topics that we haven't yet discussed are *merging* and *branching*, which are especially relevant when collaborating with others. We may come back to these in a future Discussion activity. Another topic that you might find useful to explore on your own is the `.gitignore` file. This file specifies files which should be *excluded* from tracking by git. This is handy if there are certain "junk" files that you would prefer not to see in GitHub Desktop. + +This is my first Git practice. \ No newline at end of file From 913c0f2d8492a951d64a1ebeac91537031cd1676 Mon Sep 17 00:00:00 2001 From: yaoyahan <1737469763@qq.com> Date: Tue, 8 Sep 2026 17:30:27 +0800 Subject: [PATCH 2/3] docs: improve README --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 93b2d2a..bd82b35 100644 --- a/README.md +++ b/README.md @@ -111,4 +111,5 @@ Great job! If you comfortably navigated these exercises, then you have the neces Another topic that you might find useful to explore on your own is the `.gitignore` file. This file specifies files which should be *excluded* from tracking by git. This is handy if there are certain "junk" files that you would prefer not to see in GitHub Desktop. -This is my first Git practice. \ No newline at end of file +This is my first Git practice. +Learning Git through a small open-source contribution. \ No newline at end of file From 812389ac4da17aa74fe7cc72d3f2b62ef1b88de1 Mon Sep 17 00:00:00 2001 From: yaoyahan <1737469763@qq.com> Date: Tue, 8 Sep 2026 17:37:03 +0800 Subject: [PATCH 3/3] docs: refine README wording --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index bd82b35..3442db8 100644 --- a/README.md +++ b/README.md @@ -112,4 +112,4 @@ Great job! If you comfortably navigated these exercises, then you have the neces Another topic that you might find useful to explore on your own is the `.gitignore` file. This file specifies files which should be *excluded* from tracking by git. This is handy if there are certain "junk" files that you would prefer not to see in GitHub Desktop. This is my first Git practice. -Learning Git through a small open-source contribution. \ No newline at end of file +Learning Git through a small open-source contribution! \ No newline at end of file