- All content from study groups for the online data science 022221 cohort will be added to this repository
- Each phase will have its own folder. (e.g. "
Phase_1
") - Each phase folder will contain subfolders for each topic
- e.g."
topic_01_getting_started
" - So the full folder path would be "
Phase_1
>topic_00_getting_started
- e.g."
- The
reference docs
folder contains cheat sheets and we will be adding additional resources here.
-
I recommend cloning this repository directly first, instead of forking it first.
- The Benefit:
- This makes it much easier to get the newest notes just by running
git pull
- This makes it much easier to get the newest notes just by running
- The Drawback:"
- You will not be able to make/save any changes to the repo's contents or else it will cause sync conflicts.
- The Benefit:
-
The Compromise/Solution:
-
Make a "cohort_notes" folder on you computer and
cd
into that folder with your terminal. -
FIRST clone this repo directly.
- From your terminal that is currently located in yiour new cohort_notes folder.
- Run
git clone https://github.com/flatiron-school/Online-DS-FT-022221-Cohort-Notes.git
- Run
- From your terminal that is currently located in yiour new cohort_notes folder.
-
SECOND, navigate to https://github.com/flatiron-school/Online-DS-FT-022221-Cohort-Notes,
- Make a fork from this repository
- Click on the "Settings" tab and then rename the repo to something other than "Online-DS-FT-022221-Cohort-Notes"
- Thi - Copy the URL of your newly renamed fork and run `git clone ` where you replace "" with the url you just copied.
-
Now you BOTH an easy-to-update cohort copy and your own editable/saveable version.
-
- 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).
- Even better, another Flatiron Instructor has made a video walk-through of how to set up your own fork so that its easy to get the updates from the main repository.
-
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.
- Add the following block of code to your notebook
- Change the
py_folder
path to reflect where the repo's py_files folder is relative to the notebook you are adding this to.
## Importing our study group functions
%load_ext autoreload
%autoreload 2
import sys
py_folder = "../../py_files/" # CHANGE TO REFECT YOUR NOTEBOOKS LOCATION COMPARED TO THE PY_FILES FOLDER
sys.path.append(py_folder)
import functions_SG as sg