-
NOTE RE NOTES REPOS:
-
π¨DO NOT FORK NOTES REPO BEFORE CLONING (to easily get all new notebooks.)
-
Just clone directly and run
git pull
from inside the repo's folder in your terminal to get the new notebooks.
-
- πSTUDENT RESOURCES GOOGLE DRIVE FOLDER
- See Student Resources Section farther down the page for details.
- While it is recommended to clone this repo directly to get updates easily, below are excerpts from the official GitHub documentation on the steps required to sync a fork so that it receives changes made to the upstream repo (the one you forked).
-
Open Terminal.
- cd into repo
-
List the current configured remote repository for your fork.
$ git remote -v
-
Specify a new remote upstream repository that will be synced with the fork.
$ git remote add upstream https://github.com/jirvingphd/online-dtsc-pt-041320-cohort-notes.git
-
Verify the new upstream repository you've specified for your fork.
$ git remote -v
-
Open Terminal.
-
cd into repo's folder
-
Fetch the branches and their respective commits from the upstream repository. Commits to master will be stored in a local branch,
upstream/master
.
$ git fetch upstream
- Check out your fork's local master branch.
$ git checkout master
- Merge the changes from upstream/master into your local master branch. This brings your fork's master branch into sync with the upstream repository, without losing your local changes.
$ git merge upstream/master
If your local branch didn't have any unique commits, Git will instead perform a "fast-forward":
Tip: Syncing your fork only updates your local copy of the repository. To update your fork on GitHub, you must push your changes.