Project Setup

IF YOU HAVE ALREADY CLONED THE REPO, DELETE THE FOLDER ON YOUR COMPUTER. YOU SHOULD FOLLOW THESE INSTRUCTIONS WHICH MAKE YOU CLONE IT AGAIN - JUST DO IT TO BE SAFE.

Download and install npm and node Check your node version (type node -v in command line)

If your version is not 6.11, you need to downgrade Windows: Get nvm by downloading the nvm-setup.exe file from here https://github.com/coreybutler/nvm-windows/releases Run the nvm-setup.exe file to install it

In Windows command line, type:

nvm install 6.11
nvm use 6.11

Mac: Uninstall node:

brew uninstall node
brew cleanup
nvm install 6.11
nvm use 6.11

https://nodesource.com/blog/installing-node-js-tutorial-using-nvm-on-mac-os-x-and-ubuntu/ just use step 0 to install nvm. Homebrew may cause issues in future.

Now check your node version by doing “node -v”, it should be 6.11

Log into GitHub and find Kelly’s repo kblincoe/VisualGit_SE701_2019_3 (which you should have been added to, provided you filled out the UPI form and accepted the GitHub invite in the email that Kelly sent).

Fork repo by going to Kelly’s repo and clicking “Fork” (top-right)

You should be automatically directed to your fork of the repo.

Go to your fork of Kelly’s repo, click on “Clone or Download” and copy the link (use SSH if you have SSH working on your computer (you’ll know if you’ve setup SSH before. If you want to set it up, Google it, we won’t go over that here), otherwise use the HTTPS link.

Open your git terminal and type “git clone ” It’s gonna clone now Ok when it’s one, cd into the repo folder cd VisualGit_SE701_2019_3 Run npm install Run npm install typescript-compiler Run tsc Run npm start When the application runs, the sign-in page will show. Type in your GitHub credentials to see if it signs you in. Your local repo knows about your remote repo, and your remote repo knows about the original (Kelly’s) repo. But your local repo doesn’t know about Kelly’s repo. So in your git terminal, please do:

git remote add upstream git@github.com:kblincoe/VisualGit_SE701_2019_3.git

You can get the repo link by visiting Kelly’s repo on GitHub and click on “Clone or Download” and then copy the link. Probably better to get the SSH link if you have SSH working. Now do git remote -v and you should see listed somewhere.

Okay so basically you have 3 things going on. There’s Kelly’s repo, where we make issues and stuff. This is the original repo. AKA “upstream”. You have your forked repo, (which is your remote repo). AKA “origin”. And lastly, you have your local repo.

Each time you make a branch or commit it only does it in your local repo. When you push your commits, it gets pushed to your remote repo (your fork), which is known as “origin”.

When you one to merge something into Kelly’s master, you need to go to your fork on GitHub, find your branch that you pushed, and make a pull request into the master of the original (Kelly’s) repo.

Over time, other people’s work gets merged into Kelly’s repo (upstream). You will want to regularly update your local repo (your computer) with these changes, and then also update your fork (your remote repo) with these changes.

To do this, read this https://github.com/kblincoe/VisualGit_SE701_2019_3/wiki/Updating-Your-Repo-With-Changes

Trouble shooting and the setup of this project was done by Benny and Zain