Today we will:
continue getting familiar with the structure of GitHub
clarify more how the course will flow
practice with new vocabulary
Last class was a lot of new information, today we will reinforce that mostly, and add only a little
GitHub Features and Class¶
Time management¶
See the time breakdown and make sure that you have a plan.
Notifications¶
Watch your KWL repo, by clicking the watch button at the top, toward the right. You probably want to select “all activity” for this repo.
Check your notification settings. In particular you can choose to/not get emails and which email address they go to. You can learn more about the choice in the docs.
Managing Tasks with issues¶
Navigate to your issues tab of your KWL repo
Create an issue using the content below
In the right panel, under
Developmentclick “create a branch”Leave the default settings and then create the branch
close the popup with commands, we will learn them later
Click the branch under
Developmentto go to the Code tab on that new branch (e.g.7-create-about, but your number might be different)Begin to edit the file
Commit changes directly to the branch named for the issue (e.g.
7-create-about, but your number might be different)Go to the pull Request tab
Create a pull request with
head:mainandcompare:7-create-aboutwith your actual branch nameMark the pull request as a draft using the link on the right hand side
About issue¶
title: Create About
body:
Fill in the about file tempaltePrepare for Next Class¶
important complete installs for git and bash. This must be done in order to do the in class activity on Thursday.
Choose where on your local computer you will save work for this class and make note of that for yourself
Think about how files are organized in your computer. You do not need to go learn or read about this, but spend a few minutes thinking about what you know about this or how you interact with it.
Badges¶
the text in () below is why each step is assigned
Review today’s notes both rendered and the raw markdown versions. Include links to both views in your badge PR comment. (to review the material and get familiar with the raw version)
Complete your about file on the same branch. Mark the PR ready for review. Request a review from
@brownsarahm.map out your computing knowledge and add it to your kwl chart repo. this can be an image that you upload or a text-based outline in a file called prior-knowledge-map. (optional) try mapping out using mermaid syntax, we’ll be using other tools that will faciltate rendering later (what we will learn will connect a lot of ideas, mapping out where you start, sets you up for success)
Prepare for next class¶
(for lab Monday) Read the syllabus section of the course website carefully and explore the whole course website
(for lab Monday) Bring questions about the course
(for class Tuesday) Think about one thing that you know really well (computing or not). Be prepared to discuss the following: How do you know that you know it? What was it llike to first learn it? (nothing written to submit, but you can use your issue to take notes if you would like)the text in
()below is why each step is assignedreview today’s notes after they are posted, both rendered and the raw markdown versions. Include links to both views in your badge PR comment. (to review the material and get familiar with the raw version)
Complete your about file on the same branch. Mark the PR ready for review. Request a review from
@brownsarahm.read Chapter 1, “Decoding your confusion while coding” in The Programmer’s Brain add a file called brain.md to your kwl repo that summarizes your thoughts on the chapter. Do you think this information will help you approach learning more effectively? why or why not? How, if at all, does it changes how you think about debugging and learning to program? Give examples of how you have encountered the different types of confusion in your prior programming experiences. (to help you get good strategies and prime for things we will see in the next few weeks)
map out your computing knowledge and add it to your kwl chart repo in a file called prior-knowledge-map.md. Use mermaid syntax, to draw your map. GitHub can render it for you including while you work using the preview button. (what we will learn will connect a lot of ideas, mapping out where you start, sets you up for success)
Experience Report Evidence¶
You need to have a draft PR for the about and the about issue.
Questions After Today’s Class¶
Is it better to view the issues in a Kanban board or the standard GitHub Issues view?¶
This is really a matter of personal preference. I do recommend trying the Kanban board view to see if it helps you though.