/online-dtsc-pt-041320-cohort-notes

Notebooks and resources from study group for onl01-dtsc-pt-041320 cohort

Primary LanguageJupyter NotebookGNU General Public License v3.0GPL-3.0

online-dtsc-pt-041320-cohort-notes

Notebooks and resources from study group for onl01-dtsc-pt-041320 cohort

Notebooks Are Organized By Module

  • Mod 1 folder

How to sync a fork of this repo

  • 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).
  1. Open Terminal.

    • cd into repo
  2. List the current configured remote repository for your fork. $ git remote -v

  3. 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

  4. Verify the new upstream repository you've specified for your fork. $ git remote -v

  1. Open Terminal.

  2. cd into repo's folder

  3. 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

  1. Check out your fork's local master branch.

$ git checkout master

  1. 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.