From b640ed85182216c9b77bcf00904ff2e3e31d3bb1 Mon Sep 17 00:00:00 2001 From: Vessy Shestorkina <46304479+Ve33y@users.noreply.github.com> Date: Tue, 9 May 2023 17:34:08 -0400 Subject: [PATCH] Add clarity to step 4 based on clone method Signed-off-by: Vessy Shestorkina <46304479+Ve33y@users.noreply.github.com> --- CONTRIBUTING.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1c01995f58d6c..4055c9157a750 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -23,8 +23,8 @@ Thank you for your interest in contributing to the Node.js Website. Before you p ```bash git clone git@github.com:/nodejs.org.git # SSH -gh repo clone /nodejs.org # GitHub CLI git clone https://github.com//nodejs.org.git # HTTPS +gh repo clone /nodejs.org # GitHub CLI ``` 3. Change into the nodejs.org directory. @@ -36,7 +36,9 @@ cd nodejs.org 4. Create a remote for keeping your fork as well as your local clone up-to-date. ```bash -git remote add upstream git@github.com:nodejs/nodejs.org.git +git remote add upstream git@github.com:nodejs/nodejs.org.git # SSH +git remote add upstream https://github.com/nodejs/nodejs.org.git # HTTPS +gh repo sync nodejs/nodejs.org # GitHub CLI ``` 5. Create a new branch for your work.