From 2c4157b62fb921ee77e0079fae372d1e94643a08 Mon Sep 17 00:00:00 2001
From: Trevor Moy <51927676+trevmoy@users.noreply.github.com>
Date: Tue, 24 Oct 2023 14:30:25 -0400
Subject: [PATCH 1/6] Update faq/syllabus.md

---
 faq/syllabus.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/faq/syllabus.md b/faq/syllabus.md
index 4398208..b1c4de9 100644
--- a/faq/syllabus.md
+++ b/faq/syllabus.md
@@ -66,3 +66,17 @@ excerpts or screenshots embedded in it.
 They should be markdown files in your KWL repo.  I recommend myst markdown.
 ```
 
+## Why won't my experience badge workflow contain the new changes after I edit the workflow?
+```{toggle}
+If you find that a workflow you may have made changes to are not properly reflecting your workflow changes is because you may not be running the workflow correctly.
+
+To correctly execute an action in GitHub you should:
+
+1. Make sure you are in the actions tab in your repository
+2. On the left side of the screen the specific workflows should be available to select. 
+3. Select the desired workflow.
+4. At the top of the workflow runs there should be an option to run the workflow.
+5. Select Run Workflow to run the most recent and up to date workflow.
+
+This should help correct the workflow if it was causing issues.
+```
\ No newline at end of file

From 36c4eb5fa5351cd7dd127cee55dc1e131c85c73b Mon Sep 17 00:00:00 2001
From: Trevor Moy <51927676+trevmoy@users.noreply.github.com>
Date: Tue, 24 Oct 2023 14:34:28 -0400
Subject: [PATCH 2/6] Update faq/syllabus.md

---
 faq/syllabus.md | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/faq/syllabus.md b/faq/syllabus.md
index b1c4de9..4398208 100644
--- a/faq/syllabus.md
+++ b/faq/syllabus.md
@@ -66,17 +66,3 @@ excerpts or screenshots embedded in it.
 They should be markdown files in your KWL repo.  I recommend myst markdown.
 ```
 
-## Why won't my experience badge workflow contain the new changes after I edit the workflow?
-```{toggle}
-If you find that a workflow you may have made changes to are not properly reflecting your workflow changes is because you may not be running the workflow correctly.
-
-To correctly execute an action in GitHub you should:
-
-1. Make sure you are in the actions tab in your repository
-2. On the left side of the screen the specific workflows should be available to select. 
-3. Select the desired workflow.
-4. At the top of the workflow runs there should be an option to run the workflow.
-5. Select Run Workflow to run the most recent and up to date workflow.
-
-This should help correct the workflow if it was causing issues.
-```
\ No newline at end of file

From be4e509286363fea90b8d032e03fe614abb4e6cf Mon Sep 17 00:00:00 2001
From: Trevor Moy <51927676+trevmoy@users.noreply.github.com>
Date: Tue, 28 Nov 2023 14:18:15 -0500
Subject: [PATCH 3/6] Update 2023-10-19.md

typo
---
 notes/2023-10-19.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/notes/2023-10-19.md b/notes/2023-10-19.md
index ba314df..df64776 100644
--- a/notes/2023-10-19.md
+++ b/notes/2023-10-19.md
@@ -5,7 +5,7 @@ kernelspec:
 ---
 
 
-# Why did we learn the plubming commands?
+# Why did we learn the plumbing 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.  
 
@@ -1061,4 +1061,4 @@ save your command history to `2023-10-19-log.txt` and put that file in your KWL
 
 ```{note}
 due to scheduling issues this will be late today
-```
\ No newline at end of file
+```

From 321bec4088190961fb926fe0d311dc1a4ae8219c Mon Sep 17 00:00:00 2001
From: Trevor Moy <51927676+trevmoy@users.noreply.github.com>
Date: Sat, 9 Dec 2023 18:14:40 -0500
Subject: [PATCH 4/6] added resources/offlinebadgeinstructions.md

---
 resources/offlinebadgeinstructions.md | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 resources/offlinebadgeinstructions.md

diff --git a/resources/offlinebadgeinstructions.md b/resources/offlinebadgeinstructions.md
new file mode 100644
index 0000000..2c5afd7
--- /dev/null
+++ b/resources/offlinebadgeinstructions.md
@@ -0,0 +1,3 @@
+# Offline Badge Script Tutorial
+
+If you'd like to start doing your work offline in your local kwl clone but don't have the body of the most recent issue you can follow the following steps to write your own script to get the badge instructions.
\ No newline at end of file

From 80ca05de0d39ed846244b45a0363ef583bad0aac Mon Sep 17 00:00:00 2001
From: Trevor Moy <51927676+trevmoy@users.noreply.github.com>
Date: Sat, 9 Dec 2023 18:58:18 -0500
Subject: [PATCH 5/6] Added resources/offlinebadgeinstructions.md

---
 resources/offlinebadgeinstructions.md | 44 ++++++++++++++++++++++++++-
 1 file changed, 43 insertions(+), 1 deletion(-)

diff --git a/resources/offlinebadgeinstructions.md b/resources/offlinebadgeinstructions.md
index 2c5afd7..8077fd7 100644
--- a/resources/offlinebadgeinstructions.md
+++ b/resources/offlinebadgeinstructions.md
@@ -1,3 +1,45 @@
 # Offline Badge Script Tutorial
 
-If you'd like to start doing your work offline in your local kwl clone but don't have the body of the most recent issue you can follow the following steps to write your own script to get the badge instructions.
\ No newline at end of file
+If you'd like to start doing your work offline in your local kwl clone but don't have the body of the most recent issue you can follow the following steps to write your own script to get the badge instructions.
+
+## Getting Started
+
+For later in the script you will need .jq to run the script correctly. The download can be found [here.](https://cameronnokes.com/blog/working-with-json-in-bash-using-jq/).
+
+To get started with creating a script that gets offline badge instructions you need to create a file for the script to run:
+```{toggle}
+touch badgeinstructions.sh
+```
+
+Now you will need to open that file, and type the following on the first line:
+```{toggle}
+#!/bin/bash
+```
+
+Then on the 2nd line you will need to enter:
+```{toggle}
+outputfile="offline_badge_instructions-$(date "+%Y-%m-%d").md"
+```
+
+Then, you will need to write this on the next line:
+```{toggle}
+badgeissue=$(gh issue list --label review -L 1 --json number | jq -r '.[0].number')
+```
+Here we are getting the issue list, sorting by review, getting the most recent review issue, and getting the issue number with json.
+Then we're going to pipe a jq -r '.[0].number' command to get the raw output of the gh command and we get the number of the issue for our variable.
+
+
+Next we're going to make a variable called badgeinstructions and assign the gh issue view command to it:
+```{toggle}
+badgeinstructions=$(gh issue view $badgeissue)
+```
+
+Next we're gonna echo a title for the top of the output file:
+```{toggle}
+echo "Most Recent Badge Instructions" >> $outputfile
+```
+
+Now we're gonna echo the badgeinstructions into the output file as well:
+```{toggle}
+echo "$badgeinstructions" >> $outputfile
+```
\ No newline at end of file

From 175b939333c6960c3fca3539dbc89fd3a4def41e Mon Sep 17 00:00:00 2001
From: Trevor Moy <51927676+trevmoy@users.noreply.github.com>
Date: Sat, 9 Dec 2023 19:02:55 -0500
Subject: [PATCH 6/6] Updated resources/offlinebadgeinstructions.md

---
 resources/offlinebadgeinstructions.md | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/resources/offlinebadgeinstructions.md b/resources/offlinebadgeinstructions.md
index 8077fd7..effec87 100644
--- a/resources/offlinebadgeinstructions.md
+++ b/resources/offlinebadgeinstructions.md
@@ -28,6 +28,8 @@ badgeissue=$(gh issue list --label review -L 1 --json number | jq -r '.[0].numbe
 Here we are getting the issue list, sorting by review, getting the most recent review issue, and getting the issue number with json.
 Then we're going to pipe a jq -r '.[0].number' command to get the raw output of the gh command and we get the number of the issue for our variable.
 
+*Note*: If you want to change the badge type you need to replace review with practice in the label part of the badgeissue command.
+
 
 Next we're going to make a variable called badgeinstructions and assign the gh issue view command to it:
 ```{toggle}
@@ -42,4 +44,12 @@ echo "Most Recent Badge Instructions" >> $outputfile
 Now we're gonna echo the badgeinstructions into the output file as well:
 ```{toggle}
 echo "$badgeinstructions" >> $outputfile
-```
\ No newline at end of file
+```
+
+Once we do this we should be all set to run the script:
+
+```{toggle}
+bash badgeinstructions.sh
+```
+
+Now we are all set!
\ No newline at end of file