From 3a4ed4afded20b18b721404cf858f8d5fc718bf7 Mon Sep 17 00:00:00 2001 From: ProDataMan Date: Wed, 18 May 2022 13:34:11 -0700 Subject: [PATCH] Update 04-pushing-to-a-remote.md tried this on an old widows image. it didn't work because in August 2021 GitHub stopped accepting password verification from the CLI. The new version of Git for Windows allows for the use of the credential helper or a code --- labs/1.2-basic-git-commands/04-pushing-to-a-remote.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/labs/1.2-basic-git-commands/04-pushing-to-a-remote.md b/labs/1.2-basic-git-commands/04-pushing-to-a-remote.md index a843b1f..a8d5bfa 100644 --- a/labs/1.2-basic-git-commands/04-pushing-to-a-remote.md +++ b/labs/1.2-basic-git-commands/04-pushing-to-a-remote.md @@ -5,3 +5,5 @@ Now, push your local repository to this remote: ![Pushing to a remote](../../img/git-push.png) Notice how Git tells us that our local master branch is set up to track the remote master branch. This means that any subsequent pushes no longer need the `-u origin master` part. Just a `git push` will be enough. + +Note: if this fails double check that you are running the latest version of Git