Welcome, Introduction, and Setup

1. Welcome, Introduction, and Setup#

1.1. Introductions#

  • Dr. Sarah Brown

  • Please address me as Dr. Brown or Professor Brown,

  • Ms./Mrs. are not acceptable

1.2. Prismia#

  • instead of slides

  • you can message us

  • we can see all of your responses

  • emoji!

1.3. This course will be different#

  • no Brightspace

  • 300 level = more independence

  • I will give advice, but only hold you accountable to a minimal set

  • High expectations, with a lot of flexibility

1.4. Getting started#

Your KWL chart is where you will start by tracking what you know now/before we start and what you want to learn about each topic. Then you will update it throughout the semester. You will also add material to the repository to produce evidence of your learning.

(see prismia or a member of the instructional team for the link to create your KWL if you are making up class)

1.5. We havea Glossary!!#

For example, the term we used above:

repository

Tip

In class, on prismia, I will sometimes link like above, but you can also keep the page open if that is helpful for you.

In the course site, glossary terms will be linked as in the follwing list.

Key terms for the first class:

1.6. GitHub Docs are really helpful and have screenshots#

1.7. First KWL setup steps#

Today we did the following:

  1. Accept the assignment to create your repo: KWL Chart

  2. Edit the README to add your name by clicking the pencil icon (editing a file step 2)

  3. adding a descriptive commit message and commited directly to main (editing a file step 5)

  4. Edit the README to fill in one row of the table by clicking the pencil icon (editing a file step 2)

  5. created a new branch (named prior_knowledge) (editing a file step 7-8)

  6. added a message to the Pull Request (pull request step 5)

  7. Creating a pull request (pull request step 6)

  8. Clicking Merge Pull Request

1.8. GitHub Actions#

GitHub allows us to run scripts within our repos, the feature is called GitHub Actions and the individual items are called workflows.

We ran the Experience Reflection action at the end of class.

1.9. Questions After Class#

1.9.1. is there a limit to how many branches you can have from the main branch?#

Not specifically. Technically there are limits, but they’re second hand and we will see them later

1.9.2. what should I name the commit for the experience badge?#

something like “reflected on class” or if you make an extra one where you add more detail you could use “add more detail”

1.9.3. When did Git and GitHub get created?#

git was created in 2005. GitHub was founded in 2008.

1.9.4. Do I commit directly to the branch when I edit my experience badge?#

yes

1.9.5. will these experience files be auto-generated each class?#

You will run the action manually, but it will create and name the files for you.

1.9.6. Is making Pull Requests our way of submitting work?#

Yes

1.9.7. What is the action doing#

Copying a file, naming it with that day’s date, making a branch with today’s date, and opening a PR with a specific body and title.

1.9.8. How does GitHub actions work and what is it useful for?#

This is a big picture question for the github docs to answer.

Contents