26. Wrap up#
26.1. Announcements#
there is a free practice badge available for April 11
if you already have the grade you aimed to get, you will get an issue from me to get lab credit without attendance
26.2. Minimal Reproducible Example#
26.3. Clearing Misconceptions#
26.3.1. Commit Messages#
if you use git commit without a message you have to quit that terminal and start over
Note
How can we show that this is not true?
First we need to get to a path where we are in a git directory:
ls
ex sq_sum_threaded.c
gh-inclass-sp24-brownsarahm sqsum
hi.sh sqsum.dSYM
kwl-sp24-brownsarahm sqsuml
nand2tetris sqsuml.dSYM
spring2024 test
sq_sum_locked.c tiny-book
we will use the test repo:
cd test/
to be able to make a commit, we need edits, so lets make a new file:
touch example.md
and check it with git
git status
On branch main
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: test.txt
Untracked files:
(use "git add <file>..." to include in what will be committed)
example.md
no changes added to commit (use "git add" and/or "git commit -a")
To be able to make a commit, we have to stage something
git add .
git status
On branch main
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
new file: example.md
modified: test.txt
Now that we have content staged, we can go on.
We will commit now, without the -m option fo rthe message
git commit
then it opens vim for us, a partially outlined file for us to put the commit message it.
Then we :
exit edit mode with esc
then type `:wq: to save and quit
[main 8fc580d] xample commit
2 files changed, 1 insertion(+)
create mode 100644 example.md
Finally, we have our commit!
26.3.2. Git vs GitHub#
git and GitHub are just synonyms, they refer to the same thing
Note
How can we show that this is not true?
One thing we can to is make a repo with git that is not connected to GitHub.
git init example
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
Initialized empty Git repository in /Users/brownsarahm/Documents/inclass/systems/example/.git/
Then we can cd into the repo
cd example/
we can see that it is a git repo
git status
On branch master
No commits yet
nothing to commit (create/copy files and use "git add" to track)
but that it has no remotes
git remote
You could also show alternative git hosts, for example:
26.4. Multiple Cursors#
we looked at the VSCode Multiple Cursors feature
26.5. Badges#
Your task is to help prevent students from carrying misconceptions on to future classes.
You may choose either one of these two formats. Your task is to clear misconceptions.
For every 4 vocabulary level misconceptions you address, you can earn 1 review badge, up to a maximum of 3 badges across the two types.
You may discuss your work with class mates but must submit work individually and should explain the misconception in your own words
Each question will have 3 parts:
the question with answer options; 1 correct and 3 wrong
hint/replies that could be sent to a student that picked each option
an overall explanation of the misconception(s) with links to high quality external references and/or class notes.
You will work in a dedicated repo for this so that you work with a group. The repo’s README has more detailed instructions including an option for explore badges instead.
Your task is to help prevent students from carrying misconceptions on to future classes.
You may choose either one of these two formats. Your task is to clear misconceptions.
For every 4 conceptual level misconceptions you address, you can earn 1 review badge, up to a maximum of 3 badges across the two types.
You may discuss your work with class mates but must submit work individually and should explain the misconception in your own words
Each question will have 3 parts:
the question with answer options; 1 correct and 3 wrong
hint/replies that could be sent to a student that picked each option
an overall explanation of the misconception(s) with links to high quality external references and/or class notes.
You will work in a dedicated repo for this so that you work with a group. The repo’s README has more detailed instructions including an option for explore badges instead.