Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

How does the class work?

Today we will:

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

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

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

  1. Navigate to your issues tab of your KWL repo

  2. Create an issue using the content below

  3. In the right panel, under Development click “create a branch”

  4. Leave the default settings and then create the branch

  5. close the popup with commands, we will learn them later

  6. Click the branch under Development to go to the Code tab on that new branch (e.g. 7-create-about, but your number might be different)

  7. Begin to edit the file

  8. Commit changes directly to the branch named for the issue (e.g. 7-create-about, but your number might be different)

  9. Go to the pull Request tab

  10. Create a pull request with head:main and compare:7-create-about with your actual branch name

  11. Mark 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 tempalte

Prepare for Next Class

  1. important complete installs for git and bash. This must be done in order to do the in class activity on Thursday.

  2. Choose where on your local computer you will save work for this class and make note of that for yourself

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

Review
Practice

the text in () below is why each step is assigned

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

  2. Complete your about file on the same branch. Mark the PR ready for review. Request a review from @brownsarahm.

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

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.