Chicago Flex README
A place for Chicago specific course materials.
Table of Contents:
- Chicago Flex Calendar
- Useful Links
- Due Dates
- Installations and Computer Setup
- Updating this Flex Repo
- Lab and Project Submissions
Chicago Flex Calendar
- Calendar Link: This will be the google calendar for our flex material. Please take a look at this if you have questions on the upcoming week's flexible time. I will update as we go through the course.
This will be updated as we go through the course.
- Course Info Page: DSI course outline and schedule
- Resources Page, Maintained by Adi Brohnstein: Tons of great resources thanks to the excellent local instructor in DC
- Labs are due the following Monday from publish date @ 11:59 PM
- Project Code is due @ 11:59 PM the day of your presentation. This is to allow you the afternoon and evening to clean your finished code & repository post presentation.
- Blogs are to be submitted via link on slack to Brendan. I recommend using Medium or publishing your blogs on your public portfolio.
- Quizzes will be taken in class on Fridays. You will have 30 minutes to complete the quiz, and their will be no open book or notes.
Installations and Computer Setup
Updating this Flex Repo
- In terminal, navigate to where you have the CHI-FLEX-10 repo
cdinto your directory
CHI-FLEX-10that you have cloned down using SSH from your fork!
You only need to do this part once:
- Add a new remote upstream repository to sync with your fork where ORIGINAL_OWNER is the original GitHub Enterprise account and ORIGINAL_REPOSITORY is the original repository name.
git remote add upstream email@example.com:DSI-US-10/CHI-FLEX-10.git
- we are using git to add a remote link called
upstreamthat points at the ORIGINAL_OWNER repository
- You can verify that this worked by typing in
git remote -v
Your remote upstream repository is now set up. You only need to add your remote upstream 1 time!
Do these three steps every time you want to update your local CHI-FLEX-10 Repository
git fetch upstream
git checkout master
git merge upstream/master
Lab and Project Submissions:
Once a lab / Project is posted:
- Fork lab/project Repo
- Clone down your fork of the lab/project (use ssh)
- In terminal, navigate to where you want to save the file (should be under your GA/Labs or GA/Projects directory)
git clone <your-link-here>into your terminal
cdinto the lab directory
git status(will show master)
git checkout -b ‘working’(creates a working branch on your local)
git status(should show working, which confirms you created a working branch)
- Launch jupyter notebook to view the lab!
- Make changes to/work on lab - be sure to save your work!
Once you’re finished with your lab / project:
Using terminal, type the following and read each output:
git status(should still show working as your branch)
git add name_of_file
- type `git commit -m ‘changed stuff’
git push origin working
Now will show working branch on your GitHub Enterprise forked repository. You can now issue a pull request with the original repository you forked from.
- Make sure you’re on branch ‘working’
- Click New Pull Request
- Base Fork will be DSI, Base will be Master
- Head Fork will be your repo, Compare: working
- Add comments if you want, and then Submit