Instructor Guide#

Preparation#

Activity#

  1. Discussion and Goals (10 min)

    • how we think in CS

    • role of GitHub

    • CS is more than just writing code, it’s using tools

  2. Initialize Repos with an assignment (5 min)

    • confirm that all students have the repo

    • parts of the page on GitHub, basic navigation

  3. Vocabulary Review (quiz or prismia) (10min)

    • repo

    • issue

    • pull request

    • commit

  4. Change index.md and view impact on the site (5min)

    • also check settings and turn on rendering

    • view in browser

    • view gh pages branch

  5. Examine parts and discuss the structure (15 min)

    • notice parts of html

    • what was in repo? what came from elsewhere?

    • why is htat good?

  6. Create an issue (5min)

    • programming is teamwork

  7. Close issue by updating the site (10 min)

    • github links the work with the reason for the work

    • why do we want this?

  8. Create Pull Request on a partner’s repository (20 min)

    • anyone can help improve open source content

  9. Review the pull request, update and merge (15 min)

    • code review is essential

  10. Commit History (5 min)

    • we can see a summary of what has changed

    • why might this be good

  11. Git Blame (5 min)

    • we can see who changed what when

    • why might this be good

  12. Review by adding more pages with issues and a PR (remaining time if available)

    ```{toctree}
:maxdepth: 2
:hidden:
pagename
```

  13. Feedback (5min)

    • one thing you learned

    • one htink you have a question about