From 1f09c0dc98e2805c40117744c0bdb35fd1a7fedc Mon Sep 17 00:00:00 2001 From: Lee Stott Date: Fri, 3 Oct 2025 14:28:44 +0100 Subject: [PATCH] Update 1-getting-started-lessons/2-github-basics/README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- 1-getting-started-lessons/2-github-basics/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-getting-started-lessons/2-github-basics/README.md b/1-getting-started-lessons/2-github-basics/README.md index e7017926..2219180e 100644 --- a/1-getting-started-lessons/2-github-basics/README.md +++ b/1-getting-started-lessons/2-github-basics/README.md @@ -252,7 +252,7 @@ Let's go through a contributor workflow. Assume the contributor has already _for ```bash git checkout -b [branch_name] ``` - The command will create a new branch and immediately switch to the new branch + The command will create a new branch and immediately switch to the new branch. This will bring in all changes from `main` into your branch and hopefully you can just continue. If not, VS Code will tell you where Git is _confused_ and you just alter the affected files to say which content is the most accurate.