Merge branch 'c12_notes'

Author: brownsarahm

_practice/2023-10-19.md

@@ -0,0 +1,21 @@
+1. Use your github-inclass repo to create a scenario where you can fix a problem using a git command from the [patching or debugging section of the docs](https://git-scm.com/docs). Create a log of what you did using the history or git log into a file {index}`gitstory.md`. If you have a project in another class or another badge in this class that causes you to use one in a real scenario, that can count.  If not, for example, you could create a "bug" and then use bisect to find it.  
+2. Create {index}`tagtypes.md`  with the template below.
+Include an experiment that shows which if either type of tag creates a new git object. There are two types, try creating one of each a lightwight tag (provide only the tag name- what we did in class) and an annotated (provide a name and a message with `-m`).  Determine  many of the tags in the course website are annotated vs lightweight using what  you learned about how tags are represented and `git cat-file` to see which is which. 
+
+
+```
+# Tags
+
+<!-- short defintion/description in your own words of what a tag is and what it is for -->
+
+
+## Comparing tag types 
+
+<!-- include your experiment terminal history  and interpretation -->
+
+## Inspecting tags
+
+Course website tags by type: 
+- annoted:
+- lightweight: 
+```

_prepare/2023-10-24.md

@@ -0,0 +1,3 @@
+2. If you have not already or right before class, review the GitHub Action [files in your KWL repo](../tree/main/.github/workflows/) and make note of what if any syntax in there is unfamilar.   (note that link may not work on the rendered website, but will work on issues)
+3. Use quote reply or edit to see how I made a relative path to a location within the repo in this issue. 
+4. Check out the [github action marketplace](https://github.com/marketplace?type=actions) to see other actions that are available and try to get a casual level of understanding of the *types* of things that people use actions for. 

_review/2023-10-19.md

@@ -0,0 +1,16 @@
+1. Use git bisect to find the first bad commit in the [toy bug repo](https://github.com/introcompsys/toy_bug), save the command history and the bad commit hash to {index}`git_debug.md`
+2. Create {index}`tagtypeexplore.md`  with the template below. Determine how  many of the tags in the course website are annotated vs lightweight using `git cat-file` to  inspect the tags and the `git tag` help to determine which tags are of each type. 
+
+
+```
+# Tags
+
+<!-- short defintion/description in your own words of what a tag is and what it is for -->
+
+
+## Inspecting tags
+
+Course website tags by type: 
+- annoted:
+- lightweight: 
+```

activities/practice.md

@@ -89,4 +89,11 @@ Activities:
 
 Activities:
 ```{include} ../_practice/2023-10-17.md
+```
+## 2023-10-19
+
+[related notes](../notes/2023-10-19)
+
+Activities:
+```{include} ../_practice/2023-10-19.md
 ```

activities/prepare.md

@@ -70,4 +70,11 @@ Activities:
 
 Activities:
 ```{include} ../_prepare/2023-10-19.md
+```
+## 2023-10-24
+
+
+
+Activities:
+```{include} ../_prepare/2023-10-24.md
 ```

activities/review.md

@@ -83,4 +83,11 @@ Activities:
 
 Activities:
 ```{include} ../_review/2023-10-17.md
+```
+## 2023-10-19
+
+[related notes](../notes/2023-10-19)
+
+Activities:
+```{include} ../_review/2023-10-19.md
 ```