Why did we learn the plubming commands?#
+12. Why did we learn the plubming commands?#
You will not typically use them on a day to day basis, but they are a good way to see what happens at the interim steps and make sure that you have the right understanding of what git does.
A correct understanding is essential for using more advanced features
While there is of course some content that we want you to know after this course, my goal is also to teach you process, by modeling it.
@@ -460,7 +464,7 @@Why did we learn the plubming commands?
-When is the blob created?#
+12.1. When is the blob created?#
First lets add some conent to revise a file
@@ -568,7 +572,7 @@ When is the blob created?
-How does git track file names?#
+12.2. How does git track file names?#
Let’s trace it out? First we will look at our recent commits
@@ -680,7 +684,7 @@ How does git track file names?
-What is the index?#
+12.3. What is the index?#
The staging area/index
@@ -731,7 +735,7 @@ What is the index?
-Why does it show the help#
+12.4. Why does it show the help#
Important
This was a real question from class and is a good question!
@@ -752,7 +756,7 @@ Why does it show the help
-Git References#
+12.5. Git References#
Note
I have commented out for now where the inspection of git tags did not go as expected. I hope to fill this in with the answer and notify you later.
@@ -952,7 +956,7 @@ Git References
-Making a git tag#
+12.6. Making a git tag#
We will work in the github-inclass repo for this.
@@ -1091,7 +1095,7 @@ Making a git tag
-What if I have changes I do not want to lose or commit yet#
+12.7. What if I have changes I do not want to lose or commit yet#
We want to pusht the tag, but we cannot push right now:
@@ -1160,7 +1164,7 @@ What if I have changes I do not want to lose or commit yet
-Using git to debug#
+12.8. Using git to debug#
Note
I am going to revise this later, to understand for now, refer to the git book chapter
@@ -1211,7 +1215,7 @@ Using git to debug
-What if I want to keep changes, but not commit them yet?#
+12.9. What if I want to keep changes, but not commit them yet?#
Stash creates git objects of content that you can recover later. It works like a first-in-first-out queue by default and is a conceptually separate set of content from the commit history (though it is still stored in the .git/ directory)
@@ -1226,7 +1230,7 @@ What if I want to keep changes, but not commit them yet?
-Binary searchiing with bisect#
+12.10. Binary searchiing with bisect#
Now we can tell it the good commit again
@@ -1317,7 +1321,7 @@ Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
When is the blob created?
-How does git track file names?#
+12.2. How does git track file names?#
Let’s trace it out? First we will look at our recent commits
@@ -680,7 +684,7 @@ How does git track file names?
-What is the index?#
+12.3. What is the index?#
The staging area/index
@@ -731,7 +735,7 @@ What is the index?
-Why does it show the help#
+12.4. Why does it show the help#
Important
This was a real question from class and is a good question!
@@ -752,7 +756,7 @@ Why does it show the help
-Git References#
+12.5. Git References#
Note
I have commented out for now where the inspection of git tags did not go as expected. I hope to fill this in with the answer and notify you later.
@@ -952,7 +956,7 @@ Git References
-Making a git tag#
+12.6. Making a git tag#
We will work in the github-inclass repo for this.
@@ -1091,7 +1095,7 @@ Making a git tag
-What if I have changes I do not want to lose or commit yet#
+12.7. What if I have changes I do not want to lose or commit yet#
We want to pusht the tag, but we cannot push right now:
@@ -1160,7 +1164,7 @@ What if I have changes I do not want to lose or commit yet
-Using git to debug#
+12.8. Using git to debug#
Note
I am going to revise this later, to understand for now, refer to the git book chapter
@@ -1211,7 +1215,7 @@ Using git to debug
-What if I want to keep changes, but not commit them yet?#
+12.9. What if I want to keep changes, but not commit them yet?#
Stash creates git objects of content that you can recover later. It works like a first-in-first-out queue by default and is a conceptually separate set of content from the commit history (though it is still stored in the .git/ directory)
@@ -1226,7 +1230,7 @@ What if I want to keep changes, but not commit them yet?
-Binary searchiing with bisect#
+12.10. Binary searchiing with bisect#
Now we can tell it the good commit again
@@ -1317,7 +1321,7 @@ Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
How does git track file names?
-What is the index?#
+12.3. What is the index?#
The staging area/index
@@ -731,7 +735,7 @@ What is the index?
-Why does it show the help#
+12.4. Why does it show the help#
Important
This was a real question from class and is a good question!
@@ -752,7 +756,7 @@ Why does it show the help
-Git References#
+12.5. Git References#
Note
I have commented out for now where the inspection of git tags did not go as expected. I hope to fill this in with the answer and notify you later.
@@ -952,7 +956,7 @@ Git References
-Making a git tag#
+12.6. Making a git tag#
We will work in the github-inclass repo for this.
@@ -1091,7 +1095,7 @@ Making a git tag
-What if I have changes I do not want to lose or commit yet#
+12.7. What if I have changes I do not want to lose or commit yet#
We want to pusht the tag, but we cannot push right now:
@@ -1160,7 +1164,7 @@ What if I have changes I do not want to lose or commit yet
-Using git to debug#
+12.8. Using git to debug#
Note
I am going to revise this later, to understand for now, refer to the git book chapter
@@ -1211,7 +1215,7 @@ Using git to debug
-What if I want to keep changes, but not commit them yet?#
+12.9. What if I want to keep changes, but not commit them yet?#
Stash creates git objects of content that you can recover later. It works like a first-in-first-out queue by default and is a conceptually separate set of content from the commit history (though it is still stored in the .git/ directory)
@@ -1226,7 +1230,7 @@ What if I want to keep changes, but not commit them yet?
-Binary searchiing with bisect#
+12.10. Binary searchiing with bisect#
Now we can tell it the good commit again
@@ -1317,7 +1321,7 @@ Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
What is the index?
-Why does it show the help#
+12.4. Why does it show the help#
Important
This was a real question from class and is a good question!
@@ -752,7 +756,7 @@ Why does it show the help
-Git References#
+12.5. Git References#
Note
I have commented out for now where the inspection of git tags did not go as expected. I hope to fill this in with the answer and notify you later.
@@ -952,7 +956,7 @@ Git References
-Making a git tag#
+12.6. Making a git tag#
We will work in the github-inclass repo for this.
@@ -1091,7 +1095,7 @@ Making a git tag
-What if I have changes I do not want to lose or commit yet#
+12.7. What if I have changes I do not want to lose or commit yet#
We want to pusht the tag, but we cannot push right now:
@@ -1160,7 +1164,7 @@ What if I have changes I do not want to lose or commit yet
-Using git to debug#
+12.8. Using git to debug#
Note
I am going to revise this later, to understand for now, refer to the git book chapter
@@ -1211,7 +1215,7 @@ Using git to debug
-What if I want to keep changes, but not commit them yet?#
+12.9. What if I want to keep changes, but not commit them yet?#
Stash creates git objects of content that you can recover later. It works like a first-in-first-out queue by default and is a conceptually separate set of content from the commit history (though it is still stored in the .git/ directory)
@@ -1226,7 +1230,7 @@ What if I want to keep changes, but not commit them yet?
-Binary searchiing with bisect#
+12.10. Binary searchiing with bisect#
Now we can tell it the good commit again
@@ -1317,7 +1321,7 @@ Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
Important
This was a real question from class and is a good question!
@@ -752,7 +756,7 @@Why does it show the help
-Git References#
+12.5. Git References#
Note
I have commented out for now where the inspection of git tags did not go as expected. I hope to fill this in with the answer and notify you later.
@@ -952,7 +956,7 @@ Git References
-Making a git tag#
+12.6. Making a git tag#
We will work in the github-inclass repo for this.
@@ -1091,7 +1095,7 @@ Making a git tag
-What if I have changes I do not want to lose or commit yet#
+12.7. What if I have changes I do not want to lose or commit yet#
We want to pusht the tag, but we cannot push right now:
@@ -1160,7 +1164,7 @@ What if I have changes I do not want to lose or commit yet
-Using git to debug#
+12.8. Using git to debug#
Note
I am going to revise this later, to understand for now, refer to the git book chapter
@@ -1211,7 +1215,7 @@ Using git to debug
-What if I want to keep changes, but not commit them yet?#
+12.9. What if I want to keep changes, but not commit them yet?#
Stash creates git objects of content that you can recover later. It works like a first-in-first-out queue by default and is a conceptually separate set of content from the commit history (though it is still stored in the .git/ directory)
@@ -1226,7 +1230,7 @@ What if I want to keep changes, but not commit them yet?
-Binary searchiing with bisect#
+12.10. Binary searchiing with bisect#
Now we can tell it the good commit again
@@ -1317,7 +1321,7 @@ Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
Note
I have commented out for now where the inspection of git tags did not go as expected. I hope to fill this in with the answer and notify you later.
@@ -952,7 +956,7 @@Git References
-Making a git tag#
+12.6. Making a git tag#
We will work in the github-inclass repo for this.
@@ -1091,7 +1095,7 @@ Making a git tag
-What if I have changes I do not want to lose or commit yet#
+12.7. What if I have changes I do not want to lose or commit yet#
We want to pusht the tag, but we cannot push right now:
@@ -1160,7 +1164,7 @@ What if I have changes I do not want to lose or commit yet
-Using git to debug#
+12.8. Using git to debug#
Note
I am going to revise this later, to understand for now, refer to the git book chapter
@@ -1211,7 +1215,7 @@ Using git to debug
-What if I want to keep changes, but not commit them yet?#
+12.9. What if I want to keep changes, but not commit them yet?#
Stash creates git objects of content that you can recover later. It works like a first-in-first-out queue by default and is a conceptually separate set of content from the commit history (though it is still stored in the .git/ directory)
@@ -1226,7 +1230,7 @@ What if I want to keep changes, but not commit them yet?
-Binary searchiing with bisect#
+12.10. Binary searchiing with bisect#
Now we can tell it the good commit again
@@ -1317,7 +1321,7 @@ Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
Making a git tag
-What if I have changes I do not want to lose or commit yet#
+12.7. What if I have changes I do not want to lose or commit yet#
We want to pusht the tag, but we cannot push right now:
@@ -1160,7 +1164,7 @@ What if I have changes I do not want to lose or commit yet
-Using git to debug#
+12.8. Using git to debug#
Note
I am going to revise this later, to understand for now, refer to the git book chapter
@@ -1211,7 +1215,7 @@ Using git to debug
-What if I want to keep changes, but not commit them yet?#
+12.9. What if I want to keep changes, but not commit them yet?#
Stash creates git objects of content that you can recover later. It works like a first-in-first-out queue by default and is a conceptually separate set of content from the commit history (though it is still stored in the .git/ directory)
@@ -1226,7 +1230,7 @@ What if I want to keep changes, but not commit them yet?
-Binary searchiing with bisect#
+12.10. Binary searchiing with bisect#
Now we can tell it the good commit again
@@ -1317,7 +1321,7 @@ Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
What if I have changes I do not want to lose or commit yet
-Using git to debug#
+12.8. Using git to debug#
Note
I am going to revise this later, to understand for now, refer to the git book chapter
@@ -1211,7 +1215,7 @@ Using git to debug
-What if I want to keep changes, but not commit them yet?#
+12.9. What if I want to keep changes, but not commit them yet?#
Stash creates git objects of content that you can recover later. It works like a first-in-first-out queue by default and is a conceptually separate set of content from the commit history (though it is still stored in the .git/ directory)
@@ -1226,7 +1230,7 @@ What if I want to keep changes, but not commit them yet?
-Binary searchiing with bisect#
+12.10. Binary searchiing with bisect#
Now we can tell it the good commit again
@@ -1317,7 +1321,7 @@ Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
Using git to debug#
+12.8. Using git to debug#
Note
I am going to revise this later, to understand for now, refer to the git book chapter
@@ -1211,7 +1215,7 @@Using git to debug
-What if I want to keep changes, but not commit them yet?#
+12.9. What if I want to keep changes, but not commit them yet?#
Stash creates git objects of content that you can recover later. It works like a first-in-first-out queue by default and is a conceptually separate set of content from the commit history (though it is still stored in the .git/ directory)
@@ -1226,7 +1230,7 @@ What if I want to keep changes, but not commit them yet?
-Binary searchiing with bisect#
+12.10. Binary searchiing with bisect#
Now we can tell it the good commit again
@@ -1317,7 +1321,7 @@ Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
.git/ directory)What if I want to keep changes, but not commit them yet?
-Binary searchiing with bisect#
+12.10. Binary searchiing with bisect#
Now we can tell it the good commit again
@@ -1317,7 +1321,7 @@ Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
Binary searchiing with bisect
-What about the stashed content#
+12.11. What about the stashed content#
Now that we are on main with a clean working directory it is a good time to pull the remote changes.
@@ -1461,7 +1465,7 @@ What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
@@ -1573,22 +1595,22 @@ Questions After Today’s Class
-- When is the blob created?
-- How does git track file names?
-- What is the index?
-- Why does it show the help
-- Git References
-- Making a git tag
-- What if I have changes I do not want to lose or commit yet
-- Using git to debug
-- What if I want to keep changes, but not commit them yet?
-- Binary searchiing with bisect
-- What about the stashed content
-- Prepare for Next Class
-- Review today’s class
-- More Practice
-- Experience Report Evidence
-- Questions After Today’s Class
+- 12.1. When is the blob created?
+- 12.2. How does git track file names?
+- 12.3. What is the index?
+- 12.4. Why does it show the help
+- 12.5. Git References
+- 12.6. Making a git tag
+- 12.7. What if I have changes I do not want to lose or commit yet
+- 12.8. Using git to debug
+- 12.9. What if I want to keep changes, but not commit them yet?
+- 12.10. Binary searchiing with bisect
+- 12.11. What about the stashed content
+- 12.12. Prepare for Next Class
+- 12.13. Review today’s class
+- 12.14. More Practice
+- 12.15. Experience Report Evidence
+- 12.16. Questions After Today’s Class
diff --git a/notes/2023-10-24.html b/notes/2023-10-24.html
index cac5d7c..5c7d614 100644
--- a/notes/2023-10-24.html
+++ b/notes/2023-10-24.html
@@ -9,7 +9,7 @@
- How can I use bash to automate things? — Computer Systems and Programming Tools
+ 13. How can I use bash to automate things? — Computer Systems and Programming Tools
@@ -66,6 +66,8 @@
+
+
@@ -169,7 +171,7 @@
- Office Hours & Communication
Notes
-
What about the stashed content
-Prepare for Next Class#
+12.12. Prepare for Next Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
If you have not already or right before class, review the GitHub Action files in your KWL repo 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)
Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.
Prepare for Next Class
-Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create 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.
Review today’s class
-More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below.
@@ -1512,11 +1516,11 @@
More Practice
-Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to 2023-10-19-log.txt and put that file in your KWL repo
-Questions After Today’s Class#
+12.16. Questions After Today’s Class#
Review today’s class#
+12.13. Review today’s class#
Use git bisect to find the first bad commit in the toy bug repo, save the command history and the bad commit hash to git_debug.md
Create tagtypeexplore.md with the template below. Determine how many of the tags in the course website are annotated vs lightweight using
git cat-fileto inspect the tags and thegit taghelp to determine which tags are of each type.
@@ -1488,7 +1492,7 @@
Review today’s class
More Practice#
+12.14. More Practice#
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. Create a log of what you did using the history or git log into a file 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.
Create tagtypes.md with the template below. @@ -1512,11 +1516,11 @@
More Practice -
Experience Report Evidence#
+12.15. Experience Report Evidence#
save your command history to
2023-10-19-log.txtand put that file in your KWL repo