work.html

<h1 id="work.md">Work.md</h1>
<p>Consolidated walkthrough generated from the challenge issue templates
in <code>learning-room/.github/ISSUE_TEMPLATE/</code>. Do not edit this
file manually. Run <code>npm run build:html</code> (or
<code>node scripts/generate-work-md.js</code>) to regenerate.</p>
<h2 id="core-challenges">Core challenges</h2>
<h3 id="challenge-1-find-your-way-around">Challenge 1: Find Your Way
Around</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-01-find-your-way.yml">challenge-01-find-your-way.yml</a></p>
<p><strong>Chapters:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/02-understanding-github.md">Ch02:
Understanding GitHub</a> | <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/03-navigating-repositories.md">Ch03:
Navigating Repositories</a> | <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/04-the-learning-room.md">Ch04:
The Learning Room</a></p>
<p><strong>What you will do:</strong> Explore this learning-room
repository like a scavenger hunt. You will navigate tabs, the file tree,
read key files, and find landmarks.</p>
<h4 id="step-by-step-scavenger-hunt">Step-by-step scavenger hunt</h4>
<h4 id="task-1-count-files-in-the-root">Task 1: Count files in the
root</h4>
<ol type="1">
<li>Make sure you are on the <strong>Code</strong> tab (click it at the
top)</li>
<li>Look at the file/folder list</li>
<li>Count how many items are showing (stop before the first folder)</li>
<li>Write down this number</li>
</ol>
<h4 id="task-2-find-an-open-issue">Task 2: Find an open issue</h4>
<ol type="1">
<li>Click the <strong>Issues</strong> tab</li>
<li>Look for issues with a green <strong>Open</strong> label</li>
<li>Click on one to read it</li>
<li>Write down its title</li>
</ol>
<h4 id="task-3-read-welcome.md">Task 3: Read welcome.md</h4>
<ol type="1">
<li>Click the <strong>Code</strong> tab</li>
<li>Look for a folder named <code>docs/</code></li>
<li>Click to open it</li>
<li>Find <code>welcome.md</code> and click it</li>
<li>Read the first paragraph (the opening sentence)</li>
<li>Write down what it says</li>
</ol>
<h4 id="task-4-find-the-repo-description">Task 4: Find the repo
description</h4>
<ol type="1">
<li>Go to the <strong>Code</strong> tab</li>
<li>Look at the top-right area - you should see a text description under
the repo name</li>
<li>This is the “About” section</li>
<li>Write down what it says</li>
</ol>
<h4 id="task-5-read-the-readme">Task 5: Read the README</h4>
<ol type="1">
<li>On the <strong>Code</strong> tab, scroll down to find
<code>README.md</code></li>
<li>Click it to open</li>
<li>Find the section that says “Who this workshop is for”</li>
<li>Write down the answer</li>
</ol>
<h4 id="task-6-check-the-about-section">Task 6: Check the About
section</h4>
<ol type="1">
<li>On the <strong>Code</strong> tab, look at the right sidebar</li>
<li>You should see a section labeled “About” with repo information</li>
<li>Write down what you see there</li>
</ol>
<hr />
<p><strong>Your evidence</strong> (fill in when closing this issue):</p>
<pre class="text"><code>1. I found ___ files in the root of the repository.
2. The open issue I found was titled &quot;___&quot;.
3. The first paragraph of welcome.md says...
4. The repository description is...
5. The README says this workshop is for...
6. The About section shows...</code></pre>
<hr />
<h4 id="peer-simulation-check">Peer simulation check</h4>
<p>After you submit your evidence, open the <strong>Peer Simulation:
Welcome Link Needs Context</strong> issue in this repository and leave
an encouraging comment or reaction. If your facilitator gave you access
to a real buddy repository, you may use your buddy’s issue instead.</p>
<h4 id="if-you-get-stuck">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I cannot find the tabs</td>
<td>Look for a horizontal navigation bar below the repository name.
Screen reader users: navigate by heading level 2 or use the landmark
navigation.</td>
</tr>
<tr>
<td>I cannot find <code>docs/welcome.md</code></td>
<td>On the Code tab, look for a folder called <code>docs</code>. Select
it, then select <code>welcome.md</code>.</td>
</tr>
<tr>
<td>I am not sure what counts as evidence</td>
<td>Any description of what you found works. There are no wrong answers
in a scavenger hunt.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-01-scavenger-hunt.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-2-file-your-first-issue">Challenge 2: File Your First
Issue</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-02-first-issue.yml">challenge-02-first-issue.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/05-working-with-issues.md">Ch05:
Working with Issues</a></p>
<p><strong>What you will do:</strong> Find a TODO comment in
<code>docs/welcome.md</code>, then file an issue describing the problem
with a clear title and description.</p>
<h4 id="instructions">Instructions</h4>
<ol type="1">
<li>Open <code>docs/welcome.md</code> and look for a line that contains
<code>TODO</code> – this marks something that needs fixing.</li>
<li>Go to the <strong>Issues</strong> tab and select <strong>New
issue</strong>.</li>
<li>Write a clear, descriptive title (not just “Fix TODO”).</li>
<li>In the description, use this required format: - <code>What:</code>
what needs to change - <code>Where:</code> where the problem is (must
include <code>docs/welcome.md</code>) - <code>Why:</code> why the change
matters - Mention the exact <code>TODO</code> text you found</li>
</ol>
<p>### Required format (checked automatically)</p>
<p>Use this structure in your issue description:</p>
<pre class="text"><code>What: Replace the placeholder TODO with real welcome text.
Where: docs/welcome.md, intro section.
Why: New contributors need clear context when they open the file.
TODO found: TODO: Add a short workshop welcome paragraph.
```text

#### What makes a good issue title?

| Instead of this | Write this |
|---|---|
| Fix TODO | Fix missing workshop description in welcome.md |
| Bug | welcome.md TODO placeholder needs real content |
| Update file | Replace TODO in welcome.md intro section with actual welcome text |

---

**Your evidence** (fill in when closing this issue):

```text
Issue URL: https://github.com/...
I found a TODO in docs/welcome.md that said...
My issue title was...</code></pre>
<hr />
<h4 id="peer-simulation-check-1">Peer simulation check</h4>
<p>Open the <strong>Peer Simulation: Welcome Link Needs Context</strong>
issue and leave a comment: Is the title clear? Would you know what needs
fixing just from reading the title? If your facilitator gave you access
to a real buddy repository, you may review your buddy’s issue
instead.</p>
<h4 id="if-you-get-stuck-1">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I cannot find the TODO</td>
<td>Open <code>docs/welcome.md</code> and use your browser’s find
feature (Ctrl+F or Cmd+F) to search for “TODO”.</td>
</tr>
<tr>
<td>I am not sure what to write in the description</td>
<td>Describe the problem as if you are explaining it to someone who has
never seen the file.</td>
</tr>
<tr>
<td>The New issue button is not visible</td>
<td>Make sure you are on the Issues tab. If issues are disabled, ask
your facilitator.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-02-first-issue.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-3-join-the-conversation">Challenge 3: Join the
Conversation</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-03-conversation.yml">challenge-03-conversation.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/05-working-with-issues.md">Ch05:
Working with Issues</a></p>
<p><strong>What you will do:</strong> Practice GitHub’s collaboration
features by commenting on a peer-simulation issue, using <span
class="citation" data-cites="mentions">@mentions</span>, and adding
reactions.</p>
<h4 id="instructions-1">Instructions</h4>
<ol type="1">
<li>Open the <strong>Peer Simulation: Welcome Link Needs
Context</strong> issue in this repository. If your facilitator gave you
access to a real buddy repository, you may use your buddy’s Challenge 2
issue instead.</li>
<li>Leave a <strong>meaningful comment</strong> on their issue. Ideas:
<ul>
<li>Confirm you can reproduce the problem they described</li>
<li>Suggest an approach to fix it</li>
<li>Ask a clarifying question</li>
</ul></li>
<li>Use an <strong><span class="citation"
data-cites="mention">@mention</span></strong> in your comment. For the
simulation, mention <code>@gandalf-bot</code>. For a real buddy
repository, mention your buddy’s username.</li>
<li>Add a reaction to the original issue.</li>
</ol>
<h4 id="good-commenting-tips">Good commenting tips</h4>
<ul>
<li>Be specific (“I found the same TODO on line 12” is better than “I
agree”)</li>
<li>Be encouraging (“Great find!” is always welcome)</li>
<li>Be constructive (suggest, do not just criticize)</li>
</ul>
<hr />
<p><strong>Your evidence</strong> (fill in when closing this issue):</p>
<pre class="text"><code>Comment URL: https://github.com/...
I commented on the peer-simulation issue about...
I used a reaction to...</code></pre>
<hr />
<h4 id="peer-simulation-check-2">Peer simulation check</h4>
<p>If your facilitator gave you a real buddy, check whether they
commented on your issue and reply. Otherwise, reply to Gandalf or to
your own peer-simulation comment with one follow-up thought.</p>
<h4 id="if-you-get-stuck-2">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I cannot find the peer-simulation issue</td>
<td>Go to the Issues tab and filter by the <code>peer-simulation</code>
label. If you are using a real buddy repository, ask your facilitator
for the link.</td>
</tr>
<tr>
<td>The <span class="citation" data-cites="mention">@mention</span> is
not working</td>
<td>Make sure there is no space between the @ and the username. The
username must match exactly.</td>
</tr>
<tr>
<td>I do not know how to add a reaction</td>
<td>Look for a smiley face icon at the top-right of the issue comment.
Screen reader users: the button is labeled “Add reaction”.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-03-conversation.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-4-branch-out">Challenge 4: Branch Out</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-04-branch-out.yml">challenge-04-branch-out.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/06-working-with-pull-requests.md">Ch06:
Working with Pull Requests</a></p>
<p><strong>What you will do:</strong> Create a personal branch named
<code>learn/YOUR-USERNAME</code> where you will make your Day 1
changes.</p>
<h4 id="instructions-2">Instructions</h4>
<ol type="1">
<li>Make sure you are on the <strong>Code</strong> tab of the
learning-room repository.</li>
<li>Find the branch dropdown (it shows “main” by default).</li>
<li>Type <code>learn/YOUR-USERNAME</code> (replace YOUR-USERNAME with
your actual GitHub username).</li>
<li>Select <strong>Create branch: learn/YOUR-USERNAME from
main</strong>.</li>
</ol>
<h4 id="branch-naming-convention">Branch naming convention</h4>
<p>Your branch name must follow this pattern: <code>learn/</code>
followed by your GitHub username. Examples:</p>
<ul>
<li><code>learn/octocat</code></li>
<li><code>learn/mona-lisa</code></li>
<li><code>learn/student42</code></li>
</ul>
<p>This naming convention helps facilitators and automation identify
your work.</p>
<hr />
<p><strong>Your evidence</strong> (fill in when closing this issue):</p>
<pre class="text"><code>My branch name: learn/myusername
I created it by...</code></pre>
<hr />
<h4 id="peer-simulation-check-3">Peer simulation check</h4>
<p>Open the peer-simulation PR and notice its branch name. If you have a
real buddy, ask whether they created their branch and help them find the
branch dropdown if they are stuck.</p>
<h4 id="if-you-get-stuck-3">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I cannot find the branch dropdown</td>
<td>Look for a button that says “main” with a dropdown arrow, near the
top-left of the file list. Screen reader users: it is a button labeled
“Switch branches/tags”.</td>
</tr>
<tr>
<td>It says the branch already exists</td>
<td>If you already created it, you are done. Switch to it and confirm
your username is in the name.</td>
</tr>
<tr>
<td>I typed the name wrong</td>
<td>Create a new branch with the correct name. The old one will not
cause problems.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-04-branch-out.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-5-make-your-mark">Challenge 5: Make Your Mark</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-05-make-your-mark.yml">challenge-05-make-your-mark.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/06-working-with-pull-requests.md">Ch06:
Working with Pull Requests</a></p>
<p><strong>What you will do:</strong> Edit <code>docs/welcome.md</code>
on your branch to fix the TODO you found in Challenge 2, then commit
with a meaningful message.</p>
<h4 id="instructions-3">Instructions</h4>
<ol type="1">
<li>Make sure you are on your <code>learn/YOUR-USERNAME</code> branch
(check the branch dropdown).</li>
<li>Navigate to <code>docs/welcome.md</code>.</li>
<li>Select the <strong>pencil icon</strong> (Edit this file) to open the
editor.</li>
<li>Find the TODO and replace it with real content.</li>
<li>Write a <strong>meaningful commit message</strong> that explains
what you changed and why.</li>
<li>Commit directly to your branch.</li>
</ol>
<h4 id="what-makes-a-good-commit-message">What makes a good commit
message?</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Instead of this</th>
<th>Write this</th>
</tr>
</thead>
<tbody>
<tr>
<td>Update welcome.md</td>
<td>Add workshop description to replace TODO in welcome.md</td>
</tr>
<tr>
<td>Fix stuff</td>
<td>Replace placeholder text with actual welcome message</td>
</tr>
<tr>
<td>changes</td>
<td>Add participant introduction section to welcome.md</td>
</tr>
</tbody>
</table>
<p>A good commit message answers: <strong>What</strong> did I change and
<strong>why</strong>?</p>
<hr />
<p><strong>Your evidence</strong> (fill in when closing this issue):</p>
<pre class="text"><code>Commit URL: https://github.com/...
My commit message was: &quot;...&quot;
I changed the TODO to say...</code></pre>
<hr />
<h4 id="peer-simulation-check-4">Peer simulation check</h4>
<p>Compare your commit message with the peer-simulation PR title and
commit message. Can you tell what changed just from reading it? If you
have a real buddy, compare with their commit message too.</p>
<h4 id="if-you-get-stuck-4">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I am editing on main instead of my branch</td>
<td>Switch to your branch first using the branch dropdown, then edit the
file.</td>
</tr>
<tr>
<td>I cannot find the edit button</td>
<td>Look for a pencil icon near the top-right of the file view. Screen
reader users: the button is labeled “Edit this file”.</td>
</tr>
<tr>
<td>I accidentally committed to main</td>
<td>Ask your facilitator for help. This is fixable.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-05-make-your-mark.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-6-open-your-first-pull-request">Challenge 6: Open Your
First Pull Request</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-06-first-pr.yml">challenge-06-first-pr.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/06-working-with-pull-requests.md">Ch06:
Working with Pull Requests</a></p>
<p><strong>What you will do:</strong> Open a pull request from your
<code>learn/YOUR-USERNAME</code> branch to <code>main</code>, connecting
it to the issue you filed in Challenge 2.</p>
<h4 id="instructions-4">Instructions</h4>
<ol type="1">
<li>Go to the <strong>Pull requests</strong> tab.</li>
<li>Select <strong>New pull request</strong>.</li>
<li>Set <strong>base</strong> to <code>main</code> and
<strong>compare</strong> to <code>learn/YOUR-USERNAME</code>.</li>
<li>Write a descriptive PR title.</li>
<li>In the PR description, include <code>Closes #XX</code> (replace XX
with your Challenge 2 issue number). This automatically links and closes
the issue when the PR is merged.</li>
<li>Submit the pull request.</li>
</ol>
<h4 id="pr-description-template">PR description template</h4>
<p>Use this structure for your PR description:</p>
<pre class="text"><code>### What this PR does
[One sentence describing your change]

### Why
[One sentence explaining why this change is needed]

Closes #XX
```text

#### The magic of `Closes #XX`

When you write `Closes #12` in a PR description, GitHub automatically:
- Links the PR to issue #12
- Closes issue #12 when the PR is merged

This is one of GitHub&#39;s most powerful workflow features.

---

**Your evidence** (fill in when closing this issue):

```text
PR URL: https://github.com/...
My PR links to issue #...</code></pre>
<hr />
<h4 id="peer-simulation-check-5">Peer simulation check</h4>
<p>Find the <strong>Peer Simulation: Improve contribution
guidance</strong> PR and leave an encouraging comment. If you have
access to a real buddy’s PR, you may comment there too. You will do a
full code review in Day 2.</p>
<h4 id="if-you-get-stuck-5">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I cannot find the New pull request button</td>
<td>Make sure you are on the Pull requests tab. The button is near the
top-right.</td>
</tr>
<tr>
<td>It says “There isn’t anything to compare”</td>
<td>Make sure your branch has at least one commit that differs from
main. Did you commit to the right branch?</td>
</tr>
<tr>
<td>I forgot to include <code>Closes #XX</code></td>
<td>Edit your PR description after creating it. Select the three-dot
menu or the Edit button on the description.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-06-first-pr.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-7-survive-a-merge-conflict">Challenge 7: Survive a
Merge Conflict</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-07-merge-conflict.yml">challenge-07-merge-conflict.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/07-merge-conflicts.md">Ch07:
Merge Conflicts</a></p>
<p><strong>What you will do:</strong> Your facilitator will
intentionally trigger a merge conflict in your PR. You will resolve it
by identifying conflict markers, choosing the right content, and
cleaning up the markers.</p>
<p><strong>Why this matters:</strong> Merge conflicts happen in real
teamwork. Learning to resolve them calmly is a key professional
skill.</p>
<h4 id="understanding-conflict-markers">Understanding conflict
markers</h4>
<p>When Git cannot automatically merge code, it marks the problem with
special markers:</p>
<pre class="text"><code>&lt;&lt;&lt;&lt;&lt;&lt;&lt; HEAD
The version currently on main branch
=======
Your version from your branch
&gt;&gt;&gt;&gt;&gt;&gt;&gt; learn/your-username
```text

**Your job:** Decide which version is right (or combine them), then **DELETE all three marker lines** (the `&lt;&lt;&lt;&lt;&lt;&lt;&lt;`, `=======`, `&gt;&gt;&gt;&gt;&gt;&gt;&gt;` lines). The final file should have NO markers and have actual, meaningful code.

#### Step-by-step resolution

#### Step 1: Look at your PR
1. Go to your **Pull requests** tab
2. Click on your PR
3. You should see a message: &quot;Can&#39;t automatically merge&quot; or &quot;This branch has conflicts...&quot;
4. Look for a button: **Resolve conflicts** (or &quot;Resolve&quot;)
5. Click it

#### Step 2: Find the conflict markers
1. GitHub will show the file with conflict markers highlighted
2. Look for lines starting with `&lt;&lt;&lt;&lt;&lt;&lt;&lt;`, `=======`, `&gt;&gt;&gt;&gt;&gt;&gt;&gt;`
3. Read both versions carefully

#### Step 3: Choose your version
You have three options:
- Keep the **main branch** version (delete everything from `&lt;&lt;&lt;&lt;&lt;&lt;&lt;` to `=======` inclusive, keep `=======` to `&gt;&gt;&gt;&gt;&gt;&gt;&gt;`)
- Keep **your branch** version (keep `&lt;&lt;&lt;&lt;&lt;&lt;&lt;` to `=======` exclusive, delete `=======` to `&gt;&gt;&gt;&gt;&gt;&gt;&gt;`)
- **Combine both** (keep parts of both, delete all marker lines)
- Ask your facilitator which is correct

#### Step 4: Clean up
1. Delete the marker lines: `&lt;&lt;&lt;&lt;&lt;&lt;&lt;`, `=======`, `&gt;&gt;&gt;&gt;&gt;&gt;&gt;`
2. The final file should have NO conflict markers
3. The final file should have meaningful, correct code

#### Step 5: Mark as resolved
1. At the bottom, click **Mark as resolved**
2. Commit the resolution
3. Your PR should now be mergeable

**Autograded:** The autograder will check that no conflict markers remain in your file and that the file has meaningful content.

---

**Your evidence** (fill in when closing this issue):

```text
The conflict was in file: ...
I chose to keep: ...
I resolved it by: ...</code></pre>
<hr />
<h4 id="peer-simulation-check-6">Peer simulation check</h4>
<p>Compare your resolution with the facilitator’s conflict seed or with
a real buddy if you have access. It is OK if two valid resolutions keep
different wording.</p>
<h4 id="if-you-get-stuck-6">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I do not see a conflict</td>
<td>Your facilitator may not have triggered it yet. Wait for their
signal.</td>
</tr>
<tr>
<td>I cannot find the Resolve conflicts button</td>
<td>Look in the PR conversation tab, near the merge section at the
bottom. Screen reader users: search for “Resolve conflicts” button.</td>
</tr>
<tr>
<td>I am not sure which content to keep</td>
<td>Read both versions. If both are valuable, combine them. If one is
clearly better, keep that one. There is no single right answer.</td>
</tr>
<tr>
<td>The autograder still reports conflict markers</td>
<td>Search the file for <code>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</code>,
<code>=======</code>, and <code>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</code>. All
three types must be completely removed.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-07-merge-conflict.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-8-the-culture-layer">Challenge 8: The Culture
Layer</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-08-culture.yml">challenge-08-culture.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/08-open-source-culture.md">Ch08:
Open Source Culture</a></p>
<p><strong>What you will do:</strong> Reflect on what makes open source
welcoming, then practice triaging an issue by adding descriptive
labels.</p>
<p><strong>Why this matters:</strong> Open source is about people, not
just code. Labels help teams organize work and signal what needs
attention.</p>
<h4 id="step-by-step-instructions">Step-by-step instructions</h4>
<h4 id="step-1-reflect-on-community">Step 1: Reflect on community</h4>
<p>Think about your workshop experience today and answer 2-3 of these
questions (write 1-2 sentences for each): - What made you feel welcome
or supported today? - What moment taught you something new? - What would
make this community more inclusive? - How did a peer help you or learn
from you?</p>
<h4 id="step-2-find-an-issue-to-triage">Step 2: Find an issue to
triage</h4>
<ol type="1">
<li>Click the <strong>Issues</strong> tab</li>
<li>Look for the <strong>Peer Simulation: Welcome Link Needs
Context</strong> issue (or a real classmate’s issue if you have buddy
access)</li>
<li>Click to open it</li>
</ol>
<h4 id="step-3-add-a-label">Step 3: Add a label</h4>
<ol type="1">
<li>In the issue, look on the right side for a section labeled
<strong>Labels</strong></li>
<li>Click in that section</li>
<li>You will see a dropdown menu of available labels</li>
<li>Choose ONE label that describes this issue:
<ul>
<li><code>bug</code> – something is broken or not working</li>
<li><code>enhancement</code> – a suggestion for improvement</li>
<li><code>documentation</code> – about docs, help, or guidance</li>
<li><code>good first issue</code> – suitable for newcomers</li>
<li><code>question</code> – asking for clarification</li>
</ul></li>
<li>Click the label to apply it</li>
<li>The label will appear in the issue</li>
</ol>
<h4 id="step-4-leave-a-comment-optional">Step 4: Leave a comment
(optional)</h4>
<ol type="1">
<li>Scroll down to the comment box</li>
<li>Type a short message about why you chose that label:</li>
</ol>
<pre class="text"><code>   I added the &quot;documentation&quot; label because this issue helps new contributors understand the welcome section.
```text
3. Click **Comment**

#### Step 5: Submit your evidence
1. In the form below, write:
   - Your 2-3 reflection answers
   - Which issue you triaged and what label you added
   - Why you chose that label

---

**Your evidence** (fill in when closing this issue):

```text
Reflection: ...

I triaged issue #XX by adding the label &quot;___&quot;.
I chose that label because...</code></pre>
<hr />
<h4 id="peer-simulation-check-7">Peer simulation check</h4>
<p>Share your reflection in the peer-simulation issue or with your buddy
if you have one. Different perspectives make the community richer.</p>
<h4 id="if-you-get-stuck-7">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I do not see any labels</td>
<td>You may need to create them. On the Issues tab, look for the Labels
link (next to Milestones). Or ask your facilitator to set up default
labels.</td>
</tr>
<tr>
<td>I cannot add a label to someone else’s issue</td>
<td>You may need collaborator permissions. Ask your facilitator if
labels are not available.</td>
</tr>
<tr>
<td>I do not know what to reflect on</td>
<td>Start with the simplest question: “What is one thing I learned
today?” There are no wrong answers.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-08-culture.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-9-merge-day">Challenge 9: Merge Day</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-09-merge-day.yml">challenge-09-merge-day.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/10-notifications-and-day-1-close.md">Ch10:
Notifications and Day 1 Close</a></p>
<p><strong>What you will do:</strong> Get your Day 1 PR merged, verify
your changes on main, and celebrate completing all Day 1 challenges.</p>
<p><strong>Why this matters:</strong> Merging is how work gets
integrated. This is the payoff for all your effort today.</p>
<h4 id="pre-merge-checklist">Pre-merge checklist</h4>
<p>Before clicking merge, make sure: - ✅ Your PR has no conflict
markers or merge conflicts (if it does, go back to Challenge 7) - ✅
Your PR description includes <code>Closes #XX</code> linking to your
Challenge 2 issue - ✅ Your commit message is meaningful (describes what
you changed) - ✅ You have reviewed your changes one last time</p>
<h4 id="step-by-step-merge">Step-by-step merge</h4>
<h4 id="step-1-open-your-pr">Step 1: Open your PR</h4>
<ol type="1">
<li>Click the <strong>Pull requests</strong> tab</li>
<li>Find your PR (the one you created in Challenge 6)</li>
<li>Click it to open</li>
</ol>
<h4 id="step-2-check-the-merge-button">Step 2: Check the merge
button</h4>
<ol type="1">
<li>Look at the top of the PR</li>
<li>You should see a button labeled <strong>Merge pull request</strong>
in green</li>
<li>If the button is gray and disabled, your facilitator may need to
approve it or resolve conflicts first</li>
<li>Ask your facilitator if needed</li>
</ol>
<h4 id="step-3-click-to-merge">Step 3: Click to merge</h4>
<ol type="1">
<li>Click the green <strong>Merge pull request</strong> button</li>
<li>A dropdown may appear with merge strategy options - just click
<strong>Merge</strong></li>
<li>You may see a confirmation message asking if you’re sure - click
<strong>Confirm merge</strong></li>
<li>GitHub will show “Pull request successfully merged”</li>
</ol>
<h4 id="step-4-verify-your-changes-are-on-main">Step 4: Verify your
changes are on main</h4>
<ol type="1">
<li>Click the <strong>Code</strong> tab</li>
<li>Make sure the branch dropdown shows <code>main</code></li>
<li>Navigate to <code>docs/welcome.md</code></li>
<li>You should see your new welcome text (not the TODO)</li>
<li>This confirms your change is now on the main branch for everyone to
see</li>
</ol>
<h4 id="step-5-check-that-your-issue-was-closed">Step 5: Check that your
issue was closed</h4>
<ol type="1">
<li>Click the <strong>Issues</strong> tab</li>
<li>Look at the issue you filed in Challenge 2</li>
<li>It should show <strong>Closed</strong> (because your PR said
<code>Closes #XX</code>)</li>
<li>This automation keeps issues and PRs connected</li>
</ol>
<h4 id="day-1-achievements">Day 1 achievements 🎉</h4>
<p>Stop and celebrate! You have now: - Navigated a real GitHub
repository - Filed an issue with clear, structured content -
Collaborated through comments and <span class="citation"
data-cites="mentions">@mentions</span> - Created a feature branch safely
- Made a meaningful commit with a good message - Opened a pull request
linking to your work - Resolved a merge conflict under pressure -
Reflected on community and open source culture - <strong>Merged code
that is now part of the main repository</strong></p>
<p>That is the full professional GitHub workflow. You just did it!</p>
<h4 id="day-1-celebration">Day 1 celebration</h4>
<p>You have completed Day 1. Take a moment to appreciate what you
accomplished: - You navigated a real GitHub repository - You filed an
issue and had a conversation - You created a branch, made changes, and
opened a pull request - You survived a merge conflict - You contributed
to an open source community</p>
<hr />
<p><strong>Your evidence</strong> (fill in when closing this issue):</p>
<pre class="text"><code>My PR was merged: [link]
My issue was automatically closed: [link]
One thing I am proud of from Day 1: ...</code></pre>
<hr />
<h4 id="peer-simulation-check-8">Peer simulation check</h4>
<p>Leave a wrap-up comment on the peer-simulation issue or PR. If you
have real buddy access, congratulate your buddy on completing Day 1.</p>
<h4 id="if-you-get-stuck-8">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>My PR still has conflicts</td>
<td>Go back to Challenge 7 and resolve them first.</td>
</tr>
<tr>
<td>The merge button is disabled</td>
<td>Your facilitator may need to approve the merge, or branch protection
rules may require a review. Ask your facilitator.</td>
</tr>
<tr>
<td>My issue did not close automatically</td>
<td>Check that your PR description contains <code>Closes #XX</code> with
the correct issue number. You can edit the PR description and re-merge
if needed.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-09-merge-day.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-10-go-local">Challenge 10: Go Local</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml">challenge-10-go-local.yml</a></p>
<p><strong>Chapters:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/11-vscode-interface.md">Ch11:
VS Code Interface</a> | <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/13-how-git-works.md">Ch13:
How Git Works</a> | <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md">Ch14:
Git in Practice</a></p>
<p><strong>What you will do:</strong> Clone the sci-fi themes repo to
your computer, create a feature branch, make an edit to the README.md
file, commit locally, and push to GitHub.</p>
<h4 id="the-local-workflow">The local workflow</h4>
<p>This is the professional Git workflow you will use for the rest of
your career:</p>
<ol type="1">
<li><strong>Clone</strong> the repository to your computer</li>
<li><strong>Branch</strong> – create a new branch for your work</li>
<li><strong>Edit</strong> – make your changes in your local editor</li>
<li><strong>Commit</strong> – save a snapshot locally with a
message</li>
<li><strong>Push</strong> – send your branch to GitHub</li>
</ol>
<h4 id="choose-your-tool-and-follow-the-steps">Choose your tool and
follow the steps</h4>
<h4 id="option-a-vs-code-recommended-for-day-2">Option A: VS Code
(recommended for Day 2)</h4>
<h4 id="step-1-clone-the-repository">Step 1: Clone the repository</h4>
<ol type="1">
<li>Open VS Code</li>
<li>Press Ctrl+Shift+P (or Cmd+Shift+P on Mac) to open the Command
Palette</li>
<li>Type <code>Git: Clone</code></li>
<li>Paste this repository URL:
<code>https://github.com/Community-Access/vscode-sci-fi-themes.git</code></li>
<li>Choose a folder on your computer where you want to save it</li>
<li>Wait for it to clone (you should see it in the file explorer)</li>
</ol>
<h4 id="step-2-create-your-feature-branch">Step 2: Create your feature
branch</h4>
<ol type="1">
<li>Press Ctrl+Shift+P again</li>
<li>Type <code>Git: Create Branch</code></li>
<li>Name it: <code>fix/YOUR-USERNAME</code> (replace YOUR-USERNAME with
your username)</li>
<li>Press Enter</li>
</ol>
<h4 id="step-3-edit-a-file">Step 3: Edit a file</h4>
<ol type="1">
<li>In the explorer on the left, open <code>README.md</code></li>
<li>Add a comment, fix a typo, or improve a sentence (just 1-2
lines)</li>
</ol>
<h4 id="step-4-commit-your-change">Step 4: Commit your change</h4>
<ol type="1">
<li>Press Ctrl+Shift+G to open the Source Control panel</li>
<li>You will see your modified file listed</li>
<li>Select the <strong>+</strong> next to it to <strong>Stage</strong>
the change</li>
<li>In the message field at the top, write a commit message:</li>
</ol>
<pre class="text"><code>    docs: improve README wording
```text
5. Press Ctrl+Enter (or select the checkmark) to **Commit**

#### Step 5: Push to GitHub
1. Press Ctrl+Shift+P again
2. Type `Git: Push`
3. You may see a prompt asking about &quot;set upstream&quot; - select **OK**
4. Wait for the push to complete

---

#### Option B: GitHub Desktop

#### Step 1: Clone the repository
1. Open GitHub Desktop
2. Choose File &gt; Clone Repository
3. Paste the URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
4. Choose a folder location
5. Select Clone

#### Step 2: Create your feature branch
1. Open the **Branch** menu at the top
2. Select **New Branch**
3. Name it: `fix/YOUR-USERNAME`
4. Make sure &quot;main&quot; is selected as the base
5. Select **Create Branch**

#### Step 3: Edit a file
1. Select **Show in Explorer** to open the folder
2. Open `README.md`
3. Add a comment, fix a typo, or improve a sentence

#### Step 4: Commit your change
1. Go back to GitHub Desktop
2. You should see your change listed
3. At the bottom-left, write a commit message: `docs: improve README wording`
4. Select **Commit to fix/YOUR-USERNAME**

#### Step 5: Push to GitHub
1. Select the **Publish branch** button (or **Push** if it&#39;s already published)
2. Wait for the push to complete

---

#### Option C: Command Line (CLI)

```bash
## Step 1: Clone
git clone https://github.com/Community-Access/learning-room.git
cd learning-room

## Step 2: Create your branch
git checkout -b fix/YOUR-USERNAME

## Step 3: Edit a file (use your preferred editor)
## Open docs/chapter-XX.md and make a change

## Step 4: Stage and commit
git add .
git commit -m &quot;fix: correct typo in chapter 5&quot;

## Step 5: Push
git push -u origin fix/YOUR-USERNAME
```text

**Autograded:** The autograder verifies that at least one commit exists on a non-default branch pushed from a local tool.

---

**Your evidence** (fill in when closing this issue):

```text
Tool used: VS Code / GitHub Desktop / CLI
Branch name: fix/myusername
I edited: ...
Commit message: &quot;...&quot;</code></pre>
<hr />
<h4 id="peer-simulation-check-9">Peer simulation check</h4>
<p>Compare your local tool choice with the peer-simulation PR notes or
with a real buddy. What was different about the workflow?</p>
<h4 id="if-you-get-stuck-9">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>Clone fails with authentication error</td>
<td>See <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/appendix-d-git-authentication.md">Appendix
D: Git Authentication</a> for setup help.</td>
</tr>
<tr>
<td>Push fails with permission denied</td>
<td>Make sure you have write access to the repository. Ask your
facilitator.</td>
</tr>
<tr>
<td>I am not sure what to edit</td>
<td>Fix any typo, improve any sentence, or add a helpful comment. The
content of the change matters less than the workflow.</td>
</tr>
<tr>
<td>VS Code does not show the Source Control panel</td>
<td>Press Ctrl+Shift+G (Cmd+Shift+G on Mac). Make sure you opened the
cloned folder as a workspace.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-10-go-local.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-11-open-a-day-2-pr">Challenge 11: Open a Day 2 PR</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-11-day2-pr.yml">challenge-11-day2-pr.yml</a></p>
<p><strong>Chapters:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md">Ch14:
Git in Practice</a> | <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/15-code-review.md">Ch15:
Code Review</a></p>
<p><strong>What you will do:</strong> Open a pull request from the
branch you pushed locally in Challenge 10. The workflow is identical to
Day 1 — only the source of the commits changed.</p>
<h4 id="the-workflow-pattern">The workflow pattern</h4>
<p>Notice the parallel: - <strong>Day 1:</strong> Edit on GitHub.com →
commit → open PR on GitHub - <strong>Day 2:</strong> Edit locally →
commit locally → push to GitHub → open PR</p>
<p>The PR creation step is the same. Git just moves you between
locations.</p>
<h4 id="step-by-step-instructions-1">Step-by-step instructions</h4>
<h4 id="step-1-check-for-a-notification-banner">Step 1: Check for a
notification banner</h4>
<ol type="1">
<li>Go to the sci-fi themes repository on GitHub.com</li>
<li>You may see a notification banner at the top saying “Your branch had
recent pushes”</li>
<li>If so, select <strong>Compare &amp; pull request</strong> - this is
a shortcut</li>
<li>Skip to Step 3</li>
</ol>
<h4 id="step-2-or-create-pr-manually">Step 2: Or create PR manually</h4>
<ol type="1">
<li>Select the <strong>Pull requests</strong> tab</li>
<li>Select <strong>New pull request</strong></li>
<li>Set <strong>base</strong> to <code>main</code></li>
<li>Set <strong>compare</strong> to <code>fix/YOUR-USERNAME</code> (your
Day 2 branch)</li>
<li>Select <strong>Create pull request</strong></li>
</ol>
<h4 id="step-3-write-your-pr-title">Step 3: Write your PR title</h4>
<p>Write a clear, specific title about what you changed:</p>
<pre class="text"><code>docs: improve README wording
```text

#### Step 4: Write your PR description
```text
### What this PR does
Improves the README by clarifying the instructions and fixing a typo.

### Why
Clear documentation helps new developers and theme users understand the project.
```text

#### Step 5: Submit
1. Select **Create pull request**
2. Your PR is now open for review!

---

**Your evidence** (fill in when closing this issue):

```text
PR URL: https://github.com/...
The pattern I noticed: ...</code></pre>
<hr />
<h4 id="peer-simulation-check-10">Peer simulation check</h4>
<p>Review the peer-simulation PR title and description. Is it clear what
changed? If you have real buddy access, review your buddy’s PR too.</p>
<h4 id="if-you-get-stuck-10">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I do not see my branch</td>
<td>Make sure you pushed it in Challenge 10. Run
<code>git push -u origin fix/YOUR-USERNAME</code> from your local
tool.</td>
</tr>
<tr>
<td>It says there is nothing to compare</td>
<td>Your branch may not have any new commits. Make sure you committed
and pushed at least one change.</td>
</tr>
<tr>
<td>I do not know what to write in the description</td>
<td>Use the same template from Challenge 6. Describe what you changed
and why.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-11-day2-pr.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-12-review-like-a-pro">Challenge 12: Review Like a
Pro</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-12-review.yml">challenge-12-review.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/15-code-review.md">Ch15:
Code Review</a></p>
<p><strong>What you will do:</strong> Perform a thorough code review on
a peer-simulation PR (or a buddy’s PR). Use the sample file at
<code>docs/code-review-sample.md</code> for your review if you do not
have a real PR to review. Leave inline comments, make a suggestion, and
submit a verdict.</p>
<p><strong>Why this matters:</strong> Code review is how teams maintain
quality and teach each other.</p>
<h4 id="step-by-step-review-process">Step-by-step review process</h4>
<h4 id="step-1-find-the-pr-to-review">Step 1: Find the PR to review</h4>
<ol type="1">
<li>Go to the <strong>Pull requests</strong> tab in this repository</li>
<li>Look for the <strong>Peer Simulation: Improve contribution
guidance</strong> PR</li>
<li>Click to open it</li>
<li>Alternatively, if your facilitator gave you buddy access, open your
buddy’s Day 2 PR</li>
<li>If you do not have a real PR to review, open and review the sample
file at <code>docs/code-review-sample.md</code> instead.</li>
</ol>
<h4 id="step-2-go-to-the-files-changed-tab">Step 2: Go to the Files
changed tab</h4>
<ol type="1">
<li>At the top of the PR, you will see tabs:
<strong>Conversation</strong>, <strong>Commits</strong>, <strong>Files
changed</strong>, <strong>Checks</strong></li>
<li>Click <strong>Files changed</strong></li>
<li>You will see the exact lines that were added or removed (red =
removed, green = added)</li>
</ol>
<h4 id="step-3-leave-inline-comment-1-something-positive">Step 3: Leave
inline comment #1 (something positive)</h4>
<ol type="1">
<li>Hover over a line of the changed code</li>
<li>A comment button (+) will appear on the left</li>
<li>Click it</li>
<li>Type a specific observation about something they did well:</li>
</ol>
<pre class="text"><code>   Great! This heading structure makes the section easy to scan.
```text
5. Click **Comment** (not &quot;Start a review&quot;)

#### Step 4: Leave inline comment #2 (constructive suggestion)
1. Hover over another line
2. Click the comment button
3. Type a suggestion:
```text
   This could be clearer if you said &quot;beginners&quot; instead of &quot;new people&quot;.
```text
4. Click the &quot;Suggest changes&quot; option if available (shows a +/- icon)
5. This creates a code suggestion block showing your proposed fix
6. Click **Add suggestion** or **Comment**

#### Step 5: Decide on a verdict
1. Scroll to the bottom of the **Files changed** tab
2. Look for a green **Review changes** button
3. Click it
4. Choose your verdict:
   - **Approve** = &quot;This is good to merge!&quot;
   - **Request changes** = &quot;Please fix this before merging&quot;
   - **Comment** = &quot;I have feedback but no blocking issues&quot;
5. Write a summary comment (optional):
```text
   Nice work! The structure is clear and the content is welcoming. The one suggestion would improve clarity even more.
```text
6. Click **Submit review**

#### Review checklist

When reviewing, ask yourself:
- ✅ Does it do what the PR description says?
- ✅ Is the commit message clear and meaningful?
- ✅ Are there typos or formatting issues?
- ✅ Would a beginner understand this content?
- ✅ Is the language accessible and clear?

#### Review checklist

When reviewing, consider:
- Does the change do what the PR description says?
- Is the commit message clear?
- Are there any typos or formatting issues?
- Would someone reading this file for the first time understand the changes?
- Is the content accessible (clear language, proper Markdown formatting)?

#### The three verdicts

| Verdict | When to use it |
|---|---|
| **Approve** | The changes are good and ready to merge |
| **Request changes** | Something needs to be fixed before merging |
| **Comment** | You have feedback but are not blocking the merge |

---

**Your evidence** (fill in when closing this issue):

```text
Review URL: https://github.com/...
I reviewed the peer-simulation PR.
My inline comments were about: ...
My verdict was: ... because...</code></pre>
<hr />
<h4 id="peer-simulation-check-11">Peer simulation check</h4>
<p>Read any review comments on your PR. If you do not have real buddy
access, reply to a comment on the peer-simulation PR with one thing you
learned.</p>
<h4 id="if-you-get-stuck-11">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I cannot find the Files changed tab</td>
<td>Open the PR, then look for tabs: Conversation, Commits, Files
changed. Screen reader users: these are tab links within the PR
page.</td>
</tr>
<tr>
<td>I do not know how to leave an inline comment</td>
<td>Hover over (or focus on) a line number in the diff and select the
blue + button that appears.</td>
</tr>
<tr>
<td>I do not know how to suggest changes</td>
<td>In the comment box, select the file-diff icon (it looks like +/-) to
create a suggestion block. Edit the code inside the block.</td>
</tr>
<tr>
<td>I am not sure which verdict to give</td>
<td>When in doubt, use <strong>Comment</strong>. It gives feedback
without blocking.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-12-review.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-13-ai-as-your-copilot">Challenge 13: AI as Your
Copilot</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-13-copilot.yml">challenge-13-copilot.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/16-github-copilot.md">Ch16:
GitHub Copilot</a></p>
<p><strong>What you will do:</strong> Use GitHub Copilot to improve a
documentation file, then critically evaluate the AI’s suggestions for
accuracy and value.</p>
<p><strong>Why this matters:</strong> AI is a tool, not a replacement.
Learning when to accept or reject AI suggestions is a critical
skill.</p>
<h4 id="step-by-step-instructions-2">Step-by-step instructions</h4>
<h4 id="step-1-open-the-code-review-sample-file">Step 1: Open the code
review sample file</h4>
<ol type="1">
<li>Go to the <strong>Code</strong> tab</li>
<li>Navigate to <code>docs/code-review-sample.md</code> (the same file
used in Challenge 12)</li>
<li>Open it</li>
</ol>
<h4 id="step-2-use-copilot-to-improve-it">Step 2: Use Copilot to improve
it</h4>
<ol type="1">
<li>In VS Code, open the same file locally (from Challenge 10)</li>
<li>Select a paragraph or section that could be clearer, or fix any
issues you found in Challenge 12</li>
<li>Press Ctrl+Shift+A (or click the Copilot icon)</li>
<li>Write a prompt like:</li>
</ol>
<pre class="text"><code>    Improve the clarity of this paragraph for beginners
```text
  5. Review Copilot&#39;s suggestion

#### Step 3: Evaluate the suggestion
Ask these questions before accepting:
- ✅ **Is it factually correct?** (Does it match the workshop content?)
- ✅ **Is it clearer than the original?** (Would a beginner understand it better?)
- ✅ **Does it keep the tone?** (Does it sound like the rest of the document?)
- ✅ **Is it accessible?** (No complex sentences, proper formatting?)
- ⚠️ **Did the AI add things I didn&#39;t ask for?** (Watch for extra content)

#### Step 4: Accept, modify, or reject
- **Accept** -- Click &quot;Accept&quot; or manually copy the suggestion
- **Modify** -- Take the AI&#39;s suggestion but edit it to be better
- **Reject** -- Keep the original, the AI&#39;s suggestion wasn&#39;t helpful

#### Watch for common AI mistakes

#### Hallucinated links:
```text
❌ See [the Copilot docs](https://docs.github.com/en/copilot/not-a-real-page)
✅ Verify the URL exists before accepting
```text

#### Over-complicated language:
```text
❌ Leverage synergistic paradigms to optimize workflow efficacy
✅ Work together to get things done faster
```text

#### Lost context:
```text
❌ Advanced Python techniques for machine learning...
✅ Make sure it&#39;s about the actual workshop content
```text

#### Accessibility regressions:
- Images without alt text
- Complex tables instead of lists
- Colors used to convey meaning (not accessible to colorblind users)

#### The trust-verify-reject framework

For every Copilot suggestion, ask yourself:

| Question | If yes | If no |
|---|---|---|
| Is this factually accurate? | Consider accepting | Reject immediately |
| Is this clearer than the original? | Consider accepting | Keep the original |
| Does this match the tone of the document? | Consider accepting | Modify or reject |
| Does this introduce accessibility issues? | Reject or fix | Consider accepting |
| Did the AI add content I did not ask for? | Review carefully | Likely fine |

#### What to watch for

AI can be confidently wrong. Watch for:
- **Hallucinated links** -- URLs that look real but go nowhere
- **Over-complicated language** -- simpler is usually better
- **Lost context** -- the AI may not understand the workshop&#39;s audience
- **Accessibility regressions** -- images without alt text, complex tables where lists work better

#### Step 5: Commit and push your improvement
1. Once you have accepted, modified, or rejected the Copilot suggestion, save your final version of the file
2. Stage, commit, and push your changes:
```text
   git add docs/code-review-sample.md
   git commit -m &quot;docs: improve code-review-sample clarity with Copilot assistance&quot;
   git push
```text
3. This creates a tangible record of your AI-assisted improvement in the repository

**Autograded:** The autograder verifies a commit exists on a non-default branch.

---

**Your evidence** (fill in when closing this issue):

```text
I asked Copilot to: ...
It suggested: ...
My evaluation: I accepted/modified/rejected this because...
One thing Copilot got wrong: ...
One thing Copilot got right: ...</code></pre>
<hr />
<h4 id="peer-simulation-check-12">Peer simulation check</h4>
<p>Compare your Copilot result with the peer-simulation PR or with a
real buddy if you have access. Did the AI suggestion actually improve
the document?</p>
<h4 id="if-you-get-stuck-12">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>Copilot is not available</td>
<td>You need GitHub Copilot access (free for students via GitHub
Education). Ask your facilitator for alternatives if Copilot is not
available.</td>
</tr>
<tr>
<td>I do not know what to ask Copilot</td>
<td>Try: “Improve the clarity of this paragraph” or “Suggest a better
heading for this section.”</td>
</tr>
<tr>
<td>All of Copilot’s suggestions seem good</td>
<td>Try asking it something harder, like “Rewrite this for a screen
reader user.” Evaluate whether the result actually helps.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-13-copilot.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-14-template-remix">Challenge 14: Template Remix</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-14-template.yml">challenge-14-template.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/17-issue-templates.md">Ch17:
Issue Templates</a></p>
<p><strong>What you will do:</strong> Study the familiar workshop
registration template, compare it with a worked remix sample, and create
your own custom issue template for a new purpose.</p>
<p><strong>Why this matters:</strong> Templates shape how teams
communicate. A strong template helps contributors provide the right
information the first time.</p>
<h4 id="step-by-step-instructions-3">Step-by-step instructions</h4>
<h4 id="step-1-study-the-familiar-template">Step 1: Study the familiar
template</h4>
<ol type="1">
<li>Open
<code>.github/ISSUE_TEMPLATE/workshop-registration.yml</code></li>
<li>Notice the structure: <code>name</code>, <code>description</code>,
<code>title</code>, <code>labels</code>, <code>body</code></li>
<li>Then open
<code>docs/samples/challenge-14-registration-remix-example.yml</code></li>
<li>Compare what stayed the same and what changed for the new use
case</li>
</ol>
<h4 id="step-2-create-your-template-file">Step 2: Create your template
file</h4>
<ol type="1">
<li>From Challenge 10, you already have the repository cloned
locally</li>
<li>On your <code>fix/YOUR-USERNAME</code> branch, go to
<code>.github/ISSUE_TEMPLATE/</code></li>
<li>Create a new file: <code>YOUR-USERNAME-template.yml</code></li>
<li>Use the registration template and remix sample as your starting
structure</li>
</ol>
<h4 id="step-3-choose-a-new-purpose">Step 3: Choose a new purpose</h4>
<p>Pick any structured form that would be useful. Examples: -
<strong>Accessibility feedback</strong> for reporting barriers -
<strong>Workshop improvement</strong> ideas from participants -
<strong>Bug report</strong> with steps to reproduce - <strong>Feature
request</strong> with problem and proposed solution</p>
<h4 id="step-4-include-the-required-structure">Step 4: Include the
required structure</h4>
<p>Your template must include:</p>
<div class="sourceCode" id="cb14"><pre
class="sourceCode yaml"><code class="sourceCode yaml"><span id="cb14-1"><a href="#cb14-1" aria-hidden="true" tabindex="-1"></a><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">&quot;Your Template Name&quot;</span></span>
<span id="cb14-2"><a href="#cb14-2" aria-hidden="true" tabindex="-1"></a><span class="fu">description</span><span class="kw">:</span><span class="at"> </span><span class="st">&quot;One sentence describing when to use this template&quot;</span></span>
<span id="cb14-3"><a href="#cb14-3" aria-hidden="true" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> </span><span class="st">&quot;[PREFIX]: &quot;</span></span>
<span id="cb14-4"><a href="#cb14-4" aria-hidden="true" tabindex="-1"></a><span class="fu">labels</span><span class="kw">:</span><span class="at"> </span><span class="kw">[</span><span class="st">&quot;custom-template&quot;</span><span class="kw">]</span></span>
<span id="cb14-5"><a href="#cb14-5" aria-hidden="true" tabindex="-1"></a><span class="fu">body</span><span class="kw">:</span></span>
<span id="cb14-6"><a href="#cb14-6" aria-hidden="true" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">type</span><span class="kw">:</span><span class="at"> markdown</span></span>
<span id="cb14-7"><a href="#cb14-7" aria-hidden="true" tabindex="-1"></a><span class="at">    </span><span class="fu">attributes</span><span class="kw">:</span></span>
<span id="cb14-8"><a href="#cb14-8" aria-hidden="true" tabindex="-1"></a><span class="fu">      value</span><span class="kw">: </span><span class="ch">|</span></span>
<span id="cb14-9"><a href="#cb14-9" aria-hidden="true" tabindex="-1"></a>        ## Your template heading</span>
<span id="cb14-10"><a href="#cb14-10" aria-hidden="true" tabindex="-1"></a>        Add short instructions here.</span>
<span id="cb14-11"><a href="#cb14-11" aria-hidden="true" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">type</span><span class="kw">:</span><span class="at"> textarea</span></span>
<span id="cb14-12"><a href="#cb14-12" aria-hidden="true" tabindex="-1"></a><span class="at">    </span><span class="fu">id</span><span class="kw">:</span><span class="at"> details</span></span>
<span id="cb14-13"><a href="#cb14-13" aria-hidden="true" tabindex="-1"></a><span class="at">    </span><span class="fu">attributes</span><span class="kw">:</span></span>
<span id="cb14-14"><a href="#cb14-14" aria-hidden="true" tabindex="-1"></a><span class="at">      </span><span class="fu">label</span><span class="kw">:</span><span class="at"> </span><span class="st">&quot;Details&quot;</span></span>
<span id="cb14-15"><a href="#cb14-15" aria-hidden="true" tabindex="-1"></a><span class="at">      </span><span class="fu">description</span><span class="kw">:</span><span class="at"> </span><span class="st">&quot;Describe your request.&quot;</span></span>
<span id="cb14-16"><a href="#cb14-16" aria-hidden="true" tabindex="-1"></a><span class="at">    </span><span class="fu">validations</span><span class="kw">:</span></span>
<span id="cb14-17"><a href="#cb14-17" aria-hidden="true" tabindex="-1"></a><span class="at">      </span><span class="fu">required</span><span class="kw">:</span><span class="at"> </span><span class="ch">true</span></span>
<span id="cb14-18"><a href="#cb14-18" aria-hidden="true" tabindex="-1"></a><span class="at">```text</span></span>
<span id="cb14-19"><a href="#cb14-19" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb14-20"><a href="#cb14-20" aria-hidden="true" tabindex="-1"></a><span class="co">#### Step 5: Validate and test</span></span>
<span id="cb14-21"><a href="#cb14-21" aria-hidden="true" tabindex="-1"></a><span class="at">1. Check your indentation carefully</span></span>
<span id="cb14-22"><a href="#cb14-22" aria-hidden="true" tabindex="-1"></a><span class="at">2. Commit and push your branch</span></span>
<span id="cb14-23"><a href="#cb14-23" aria-hidden="true" tabindex="-1"></a><span class="at">3. Open a PR on GitHub</span></span>
<span id="cb14-24"><a href="#cb14-24" aria-hidden="true" tabindex="-1"></a><span class="at">4. If you want extra practice, open the issue chooser and confirm your template appears</span></span>
<span id="cb14-25"><a href="#cb14-25" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb14-26"><a href="#cb14-26" aria-hidden="true" tabindex="-1"></a><span class="ot">**Autograded:**</span><span class="at"> The autograder verifies that a YAML file exists in `.github/ISSUE_TEMPLATE/` with a valid `name` field.</span></span>
<span id="cb14-27"><a href="#cb14-27" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb14-28"><a href="#cb14-28" aria-hidden="true" tabindex="-1"></a><span class="pp">---</span></span>
<span id="cb14-29"><a href="#cb14-29" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb14-30"><a href="#cb14-30" aria-hidden="true" tabindex="-1"></a><span class="ot">**Your</span><span class="at"> </span><span class="fu">evidence** (fill in when closing this issue)</span><span class="kw">:</span></span>
<span id="cb14-31"><a href="#cb14-31" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb14-32"><a href="#cb14-32" aria-hidden="true" tabindex="-1"></a><span class="at">```text</span></span>
<span id="cb14-33"><a href="#cb14-33" aria-hidden="true" tabindex="-1"></a><span class="fu">Template file URL</span><span class="kw">:</span><span class="at"> https://github.com/...</span></span>
<span id="cb14-34"><a href="#cb14-34" aria-hidden="true" tabindex="-1"></a><span class="fu">I remixed the registration template into</span><span class="kw">:</span><span class="at"> ...</span></span>
<span id="cb14-35"><a href="#cb14-35" aria-hidden="true" tabindex="-1"></a><span class="fu">My template is for</span><span class="kw">:</span><span class="at"> ...</span></span>
<span id="cb14-36"><a href="#cb14-36" aria-hidden="true" tabindex="-1"></a><span class="fu">I included these fields</span><span class="kw">:</span><span class="at"> ...</span></span></code></pre></div>
<hr />
<h4 id="peer-simulation-check-13">Peer simulation check</h4>
<p>Compare your template with the seeded challenge templates. What
information does your template capture more clearly than a blank issue
would?</p>
<h4 id="if-you-get-stuck-13">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I cannot find the familiar template</td>
<td>Open <code>.github/ISSUE_TEMPLATE/workshop-registration.yml</code>
in this repository. That is the form you used during onboarding.</td>
</tr>
<tr>
<td>YAML syntax error</td>
<td>YAML is indentation-sensitive. Use 2 spaces, not tabs, and make sure
each key is followed by a colon.</td>
</tr>
<tr>
<td>I do not know what topic to choose</td>
<td>Start with something simple: a bug report, feedback form, or feature
request.</td>
</tr>
<tr>
<td>The template does not appear in the issue chooser</td>
<td>Make sure the file is in <code>.github/ISSUE_TEMPLATE/</code>, ends
in <code>.yml</code>, and includes a <code>name</code> field.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-14-template.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-15-meet-the-agents">Challenge 15: Meet the Agents</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-15-agents.yml">challenge-15-agents.yml</a></p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/19-accessibility-agents.md">Ch19:
Accessibility Agents</a></p>
<p><strong>What you will do:</strong> Explore the accessibility-agents
repo, discover what agents exist, run one, and read one agent’s
instructions file.</p>
<h4 id="step-by-step">Step-by-step</h4>
<h4 id="step-1-discover-agents-5-min">Step 1: Discover agents (5
min)</h4>
<ol type="1">
<li>Go to https://github.com/Community-Access/accessibility-agents</li>
<li>Browse the folders - each one is an agent</li>
<li>Find and list at least 3 agent names and what they do</li>
</ol>
<h4 id="step-2-run-an-agent-10-min">Step 2: Run an agent (10 min)</h4>
<ol type="1">
<li>Choose one agent that interests you</li>
<li>Follow its README for how to run it (Copilot command, VS Code
palette, etc.)</li>
<li>Test it on a file or task</li>
<li>Describe what it did</li>
</ol>
<h4 id="step-3-read-an-agents-instructions-10-min">Step 3: Read an
agent’s instructions (10 min)</h4>
<ol type="1">
<li>Open any agent’s <code>.agent.md</code> file</li>
<li>Find these sections:
<ul>
<li><strong>Purpose</strong> – what is this agent for?</li>
<li><strong>Responsibilities</strong> – what can it do?</li>
<li><strong>Guardrails</strong> – what should it NOT do?</li>
</ul></li>
<li>Note your findings</li>
</ol>
<h4 id="what-to-look-for-in-an-.agent.md-file">What to look for in an
<code>.agent.md</code> file</h4>
<p>Every agent file follows a pattern: - <strong>YAML
frontmatter</strong> at the top: metadata like name, description, tools
- <strong>Responsibilities</strong> section: what the agent is designed
to do - <strong>Guardrails</strong> section: boundaries that keep the
agent safe and focused</p>
<h4 id="what-unlocks-next">What unlocks next</h4>
<p>When you close Challenge 15, <strong>Challenge 16</strong> and
<strong>all five bonus challenges</strong> unlock. You can move into the
capstone, choose any bonus challenge, or mix them in the order that
helps you most.</p>
<h4 id="step-4-document-your-discoveries-5-min">Step 4: Document your
discoveries (5 min)</h4>
<ol type="1">
<li>Open <code>docs/my-notes/agents-discovery.md</code> in this
repository (from your local clone in Challenge 10, or via the GitHub
editor)</li>
<li>Add a section with your discoveries: ```markdown ## YOUR-USERNAME:
Agent Discoveries</li>
</ol>
<h4 id="agents-i-found">Agents I found:</h4>
<ul>
<li>Agent name: what it does</li>
<li>Agent name: what it does</li>
<li>Agent name: what it does</li>
</ul>
<p><strong>Agent I ran:</strong> [name] - It did: [what happened]</p>
<p><strong>Agent I read:</strong> [name] - Purpose: … Guardrails
include: …</p>
<pre class="text"><code>3. Commit and push your changes:
```text
   git add docs/my-notes/agents-discovery.md
   git commit -m &quot;docs: add agent discoveries for [YOUR-USERNAME]&quot;
   git push
```text
4. Open a PR to add your notes to the repository

---

**Your evidence** (fill in when closing this issue):

```text
Three agents I found:
1. ...
2. ...
3. ...

I ran the &quot;___&quot; agent. It did: ...

I read the &quot;___&quot; agent file. Its purpose is..., its guardrails include...

PR or commit URL: https://github.com/...</code></pre>
<hr />
<h4 id="peer-simulation-check-14">Peer simulation check</h4>
<p>Compare your agent discoveries with the peer-simulation issue or with
a real buddy if you have access. Did you find different agents or
different use cases?</p>
<h4 id="if-you-get-stuck-14">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I cannot find the accessibility-agents repo</td>
<td>Go to the Community-Access organization on GitHub and look for the
accessibility-agents repository.</td>
</tr>
<tr>
<td>I do not know how to run an agent</td>
<td>Look for a README or usage instructions in the agent’s folder. Some
agents work in Copilot Chat, others in VS Code.</td>
</tr>
<tr>
<td>The agent file is confusing</td>
<td>Focus on the YAML frontmatter first, then the section headings. Your
Chapter 19 reading explains the format.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-15-agents.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="challenge-16-capstone-project">Challenge 16: Capstone
Project</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/challenge-16-capstone.yml">challenge-16-capstone.yml</a></p>
<p><strong>Chapters:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/18-fork-and-contribute.md">Ch18:
Fork and Contribute</a> | <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/20-build-your-agent.md">Ch20:
Build Your Agent</a></p>
<p><strong>What you will do:</strong> Choose <strong>Accessibility
Agents</strong>, <strong>GLOW</strong>, or another meaningful
repository. Then create or improve an agentic contribution such as an
agent, prompt, custom instructions file, skill, workflow, issue
template, or documentation update.</p>
<p><strong>What counts as success:</strong> Your evidence should show a
clear mission, concrete responsibilities, sensible guardrails, and work
that is ready for review.</p>
<p><strong>When this opens:</strong> Challenge 16 unlocks right after
Challenge 15, at the same time as Bonus A-E. You can work on the
capstone first, pick a bonus first, or alternate between them.</p>
<h4 id="phase-1-choose-your-contribution-path">Phase 1: Choose your
contribution path</h4>
<ol type="1">
<li>Pick one path: <strong>Accessibility Agents</strong>,
<strong>GLOW</strong>, or another repository you care about</li>
<li>Write a one-sentence mission statement for your contribution</li>
<li>Decide what you will create or improve</li>
</ol>
<h4 id="phase-2-fork-or-prepare-your-workspace">Phase 2: Fork or prepare
your workspace</h4>
<ol type="1">
<li>If the repository accepts fork-based contributions, fork it to your
account</li>
<li>Clone your fork locally</li>
<li>Create a branch for your work</li>
<li>If you cannot open a PR, prepare a review-ready draft or
contribution plan instead</li>
</ol>
<h4 id="phase-3-build-the-contribution">Phase 3: Build the
contribution</h4>
<p>Choose one contribution type: - <strong>Agent file</strong> -
<strong>Prompt or slash command</strong> - <strong>Custom
instructions</strong> - <strong>Skill or workflow update</strong> -
<strong>Issue template or documentation improvement</strong></p>
<p>If you build an agent file, include:</p>
<div class="sourceCode" id="cb16"><pre
class="sourceCode markdown"><code class="sourceCode markdown"><span id="cb16-1"><a href="#cb16-1" aria-hidden="true" tabindex="-1"></a><span class="co">---</span></span>
<span id="cb16-2"><a href="#cb16-2" aria-hidden="true" tabindex="-1"></a><span class="an">name:</span><span class="co"> &quot;Your Agent Name&quot;</span></span>
<span id="cb16-3"><a href="#cb16-3" aria-hidden="true" tabindex="-1"></a><span class="an">description:</span><span class="co"> &quot;One sentence describing what your agent does&quot;</span></span>
<span id="cb16-4"><a href="#cb16-4" aria-hidden="true" tabindex="-1"></a><span class="an">tools:</span><span class="co"> [&quot;codebase&quot;]</span></span>
<span id="cb16-5"><a href="#cb16-5" aria-hidden="true" tabindex="-1"></a><span class="co">---</span></span>
<span id="cb16-6"><a href="#cb16-6" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb16-7"><a href="#cb16-7" aria-hidden="true" tabindex="-1"></a><span class="fu">## Your Agent Name</span></span>
<span id="cb16-8"><a href="#cb16-8" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb16-9"><a href="#cb16-9" aria-hidden="true" tabindex="-1"></a><span class="fu">### Responsibilities</span></span>
<span id="cb16-10"><a href="#cb16-10" aria-hidden="true" tabindex="-1"></a><span class="ss">- </span>Responsibility 1</span>
<span id="cb16-11"><a href="#cb16-11" aria-hidden="true" tabindex="-1"></a><span class="ss">- </span>Responsibility 2</span>
<span id="cb16-12"><a href="#cb16-12" aria-hidden="true" tabindex="-1"></a><span class="ss">- </span>Responsibility 3</span>
<span id="cb16-13"><a href="#cb16-13" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb16-14"><a href="#cb16-14" aria-hidden="true" tabindex="-1"></a><span class="fu">### Guardrails</span></span>
<span id="cb16-15"><a href="#cb16-15" aria-hidden="true" tabindex="-1"></a><span class="ss">- </span>Never do X</span>
<span id="cb16-16"><a href="#cb16-16" aria-hidden="true" tabindex="-1"></a><span class="ss">- </span>Always verify Y before Z</span>
<span id="cb16-17"><a href="#cb16-17" aria-hidden="true" tabindex="-1"></a><span class="in">```text</span></span>
<span id="cb16-18"><a href="#cb16-18" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb16-19"><a href="#cb16-19" aria-hidden="true" tabindex="-1"></a><span class="in">You can also use `docs/samples/agent-file-template.md` as a starting point when your capstone includes an agent.</span></span>
<span id="cb16-20"><a href="#cb16-20" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb16-21"><a href="#cb16-21" aria-hidden="true" tabindex="-1"></a><span class="in">#### Phase 4: Prepare review evidence</span></span>
<span id="cb16-22"><a href="#cb16-22" aria-hidden="true" tabindex="-1"></a><span class="in">1. Commit and push your work, or save a review-ready draft</span></span>
<span id="cb16-23"><a href="#cb16-23" aria-hidden="true" tabindex="-1"></a><span class="in">2. Open a PR if your chosen repository allows it</span></span>
<span id="cb16-24"><a href="#cb16-24" aria-hidden="true" tabindex="-1"></a><span class="in">3. If you cannot open a PR, create a contribution issue or written plan that explains your mission, responsibilities, guardrails, and next steps</span></span>
<span id="cb16-25"><a href="#cb16-25" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb16-26"><a href="#cb16-26" aria-hidden="true" tabindex="-1"></a><span class="in">#### Phase 5: Review and reflect</span></span>
<span id="cb16-27"><a href="#cb16-27" aria-hidden="true" tabindex="-1"></a><span class="in">1. Review a classmate&#39;s capstone PR if facilitator access is available</span></span>
<span id="cb16-28"><a href="#cb16-28" aria-hidden="true" tabindex="-1"></a><span class="in">2. If not, review the peer-simulation PR and explain what you would look for in a capstone contribution</span></span>
<span id="cb16-29"><a href="#cb16-29" aria-hidden="true" tabindex="-1"></a><span class="in">3. Check for clarity, scope, responsibilities, guardrails, and usefulness to the target repository</span></span>
<span id="cb16-30"><a href="#cb16-30" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb16-31"><a href="#cb16-31" aria-hidden="true" tabindex="-1"></a><span class="in">**Autograded:** If you choose the Accessibility Agents path and submit an `.agent.md` file, the autograder verifies that it has valid YAML frontmatter plus **Responsibilities** and **Guardrails** sections. If you choose GLOW or another repository, facilitators review your evidence using the same mission, responsibilities, and guardrails criteria.</span></span>
<span id="cb16-32"><a href="#cb16-32" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb16-33"><a href="#cb16-33" aria-hidden="true" tabindex="-1"></a><span class="in">---</span></span>
<span id="cb16-34"><a href="#cb16-34" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb16-35"><a href="#cb16-35" aria-hidden="true" tabindex="-1"></a><span class="in">**Your evidence** (fill in when closing this issue):</span></span>
<span id="cb16-36"><a href="#cb16-36" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb16-37"><a href="#cb16-37" aria-hidden="true" tabindex="-1"></a><span class="in">```text</span></span>
<span id="cb16-38"><a href="#cb16-38" aria-hidden="true" tabindex="-1"></a><span class="in">Repository I chose: Accessibility Agents / GLOW / another repository</span></span>
<span id="cb16-39"><a href="#cb16-39" aria-hidden="true" tabindex="-1"></a><span class="in">Repository URL or fork: https://github.com/...</span></span>
<span id="cb16-40"><a href="#cb16-40" aria-hidden="true" tabindex="-1"></a><span class="in">Contribution type: agent / prompt / instructions / skill / workflow / template / docs</span></span>
<span id="cb16-41"><a href="#cb16-41" aria-hidden="true" tabindex="-1"></a><span class="in">Mission statement: ...</span></span>
<span id="cb16-42"><a href="#cb16-42" aria-hidden="true" tabindex="-1"></a><span class="in">PR, branch, or plan URL: https://github.com/...</span></span>
<span id="cb16-43"><a href="#cb16-43" aria-hidden="true" tabindex="-1"></a><span class="in">Responsibilities I defined: ...</span></span>
<span id="cb16-44"><a href="#cb16-44" aria-hidden="true" tabindex="-1"></a><span class="in">Guardrails I defined: ...</span></span>
<span id="cb16-45"><a href="#cb16-45" aria-hidden="true" tabindex="-1"></a><span class="in">I reviewed a peer or peer-simulation contribution by checking: ...</span></span></code></pre></div>
<hr />
<h4 id="peer-simulation-check-15">Peer simulation check</h4>
<p>If you cannot review a real capstone contribution, use the
peer-simulation PR and explain what you would check for before calling
the work review-ready.</p>
<h4 id="if-you-get-stuck-15">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I do not know which repository to choose</td>
<td>Start with Accessibility Agents if you want the most direct
agent-building path. Choose GLOW or another repository if you already
see a useful contribution there.</td>
</tr>
<tr>
<td>I do not know what to contribute</td>
<td>Pick one small, clear improvement: an agent, prompt, instructions
file, issue template, or documentation page.</td>
</tr>
<tr>
<td>I cannot open a PR to the original repository</td>
<td>Push to your fork first, then open a PR from your fork. If the
project does not accept PRs during the workshop, submit a review-ready
contribution plan instead.</td>
</tr>
<tr>
<td>The autograder fails</td>
<td>The autograder only validates the Accessibility Agents
<code>.agent.md</code> path. For other paths, make sure your evidence
clearly explains mission, responsibilities, guardrails, and review
readiness.</td>
</tr>
<tr>
<td>I finished but want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-16-capstone.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<h2 id="bonus-challenges">Bonus challenges</h2>
<h3 id="bonus-a-improve-an-existing-agent">Bonus A: Improve an Existing
Agent</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/bonus-a-improve-agent.yml">bonus-a-improve-agent.yml</a></p>
<p><strong>For students who:</strong> Finish early and want to
strengthen an existing agent in Accessibility Agents, GLOW, or another
repo that already uses agents.</p>
<p><strong>What you will do:</strong> Choose an existing agent, make one
focused improvement, and prepare a PR or review-ready branch.</p>
<p><strong>When this unlocks:</strong> Bonus challenges unlock after
Challenge 15. You do not need to finish Challenge 16 before starting
this one.</p>
<h4 id="step-by-step-1">Step-by-step</h4>
<h4 id="step-1-pick-an-agent-5-min">Step 1: Pick an agent (5 min)</h4>
<ol type="1">
<li>Open the repository you chose for your capstone, or start with
<code>github.com/Community-Access/accessibility-agents</code></li>
<li>Browse the agent folders</li>
<li>Read 2-3 <code>.agent.md</code> files</li>
<li>Choose one to improve</li>
</ol>
<h4 id="step-2-identify-an-improvement-5-min">Step 2: Identify an
improvement (5 min)</h4>
<p>Look for: - Vague responsibility that needs clarification - Missing
guardrail (what it should NOT do) - Typo or unclear description - New
responsibility that fits</p>
<h4 id="step-3-make-the-improvement-10-min">Step 3: Make the improvement
(10 min)</h4>
<ol type="1">
<li>On your fork or working branch, create
<code>agent-improve/AGENT-NAME</code></li>
<li>Edit the agent’s <code>.agent.md</code> file</li>
<li>Make your improvement clear and focused</li>
<li>Commit:
<code>Improve [agent name]: [specific improvement]</code></li>
<li>Push to your fork</li>
</ol>
<h4 id="step-4-open-cross-fork-pr-5-min">Step 4: Open cross-fork PR (5
min)</h4>
<ol type="1">
<li>Go to the original repository for the agent you improved</li>
<li>Click “New pull request”</li>
<li>Set the base branch to the original repository’s main branch</li>
<li>Set compare to your fork and
<code>agent-improve/AGENT-NAME</code></li>
<li>Title: <code>Improve [agent]: [specific improvement]</code></li>
<li>Explain why this makes the agent better</li>
</ol>
<p>If the repository does not allow a workshop PR, share a review-ready
branch or contribution plan instead.</p>
<h4 id="improvement-criteria">Improvement criteria</h4>
<p>Good improvements are: - <strong>Specific</strong> – change one thing
well, not many things vaguely - <strong>Justified</strong> – explain WHY
the change makes the agent better - <strong>Respectful</strong> – the
original author made choices for reasons. Improve, do not rewrite.</p>
<hr />
<p><strong>Your evidence</strong> (fill in when closing this issue):</p>
<pre class="text"><code>Repository: Accessibility Agents / GLOW / another repo
Agent I improved: ...
What I changed: ...
Why this is an improvement: ...
PR or branch URL: https://github.com/...</code></pre>
<hr />
<h4 id="if-you-get-stuck-16">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>Every agent looks perfect</td>
<td>Read for clarity, scope, and guardrails. A small wording improvement
is fine if you can justify it.</td>
</tr>
<tr>
<td>I am not sure my change is an improvement</td>
<td>If you can explain why it helps, it is an improvement. When in
doubt, err on the side of clarity.</td>
</tr>
<tr>
<td>I want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-bonus-a.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="bonus-b-document-your-journey">Bonus B: Document Your
Journey</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/bonus-b-document-journey.yml">bonus-b-document-journey.yml</a></p>
<p><strong>For students who:</strong> Enjoy writing and reflection.</p>
<p><strong>What you will do:</strong> Write a reflection document about
your workshop experience and what you learned.</p>
<p><strong>When this unlocks:</strong> Bonus challenges unlock after
Challenge 15. You can do this before, during, or after Challenge 16.</p>
<h4 id="step-by-step-2">Step-by-step</h4>
<h4 id="step-1-create-your-file-2-min">Step 1: Create your file (2
min)</h4>
<ol type="1">
<li>On your branch, create:
<code>reflections/YOUR-USERNAME.md</code></li>
</ol>
<h4 id="step-2-document-key-sections-20-min">Step 2: Document key
sections (20 min)</h4>
<p>Write about: - <strong>What I learned:</strong> Your top 3 GitHub
skills - <strong>How I felt:</strong> Surprising? Challenging? Fun? -
<strong>My biggest win:</strong> One accomplishment you’re proud of -
<strong>What’s next:</strong> How will you use these skills? -
<strong>Advice to next cohort:</strong> One thing you’d tell future
students</p>
<h4 id="step-3-format-properly-5-min">Step 3: Format properly (5
min)</h4>
<ul>
<li>Use markdown headings (##, ###)</li>
<li>Use lists for clarity</li>
<li>Keep it 300-500 words</li>
</ul>
<h4 id="step-4-share-your-story-5-min">Step 4: Share your story (5
min)</h4>
<ul>
<li>Commit to your branch</li>
<li>Push to GitHub</li>
<li>Optional: Share in #wins or discussions</li>
</ul>
<div class="sourceCode" id="cb18"><pre
class="sourceCode markdown"><code class="sourceCode markdown"><span id="cb18-1"><a href="#cb18-1" aria-hidden="true" tabindex="-1"></a><span class="fu">## My Git Going with GitHub Journey</span></span>
<span id="cb18-2"><a href="#cb18-2" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb18-3"><a href="#cb18-3" aria-hidden="true" tabindex="-1"></a><span class="fu">### Before the workshop</span></span>
<span id="cb18-4"><a href="#cb18-4" aria-hidden="true" tabindex="-1"></a><span class="co">[</span><span class="ot">What did you know about GitHub before? What were you nervous about?</span><span class="co">]</span></span>
<span id="cb18-5"><a href="#cb18-5" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb18-6"><a href="#cb18-6" aria-hidden="true" tabindex="-1"></a><span class="fu">### Day 1 highlights</span></span>
<span id="cb18-7"><a href="#cb18-7" aria-hidden="true" tabindex="-1"></a><span class="co">[</span><span class="ot">What moment stands out from Day 1? What surprised you?</span><span class="co">]</span></span>
<span id="cb18-8"><a href="#cb18-8" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb18-9"><a href="#cb18-9" aria-hidden="true" tabindex="-1"></a><span class="fu">### Day 2 highlights</span></span>
<span id="cb18-10"><a href="#cb18-10" aria-hidden="true" tabindex="-1"></a><span class="co">[</span><span class="ot">What clicked on Day 2 that did not make sense before?</span><span class="co">]</span></span>
<span id="cb18-11"><a href="#cb18-11" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb18-12"><a href="#cb18-12" aria-hidden="true" tabindex="-1"></a><span class="fu">### What I built</span></span>
<span id="cb18-13"><a href="#cb18-13" aria-hidden="true" tabindex="-1"></a><span class="co">[</span><span class="ot">Describe your capstone contribution and why you chose that topic or repository.</span><span class="co">]</span></span>
<span id="cb18-14"><a href="#cb18-14" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb18-15"><a href="#cb18-15" aria-hidden="true" tabindex="-1"></a><span class="fu">### What I would tell future students</span></span>
<span id="cb18-16"><a href="#cb18-16" aria-hidden="true" tabindex="-1"></a><span class="co">[</span><span class="ot">One piece of advice for someone starting this workshop tomorrow.</span><span class="co">]</span></span>
<span id="cb18-17"><a href="#cb18-17" aria-hidden="true" tabindex="-1"></a><span class="in">```text</span></span>
<span id="cb18-18"><a href="#cb18-18" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb18-19"><a href="#cb18-19" aria-hidden="true" tabindex="-1"></a><span class="in">3. Commit with a meaningful message and open a PR.</span></span>
<span id="cb18-20"><a href="#cb18-20" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb18-21"><a href="#cb18-21" aria-hidden="true" tabindex="-1"></a><span class="in">---</span></span>
<span id="cb18-22"><a href="#cb18-22" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb18-23"><a href="#cb18-23" aria-hidden="true" tabindex="-1"></a><span class="in">**Your evidence** (fill in when closing this issue):</span></span>
<span id="cb18-24"><a href="#cb18-24" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb18-25"><a href="#cb18-25" aria-hidden="true" tabindex="-1"></a><span class="in">```text</span></span>
<span id="cb18-26"><a href="#cb18-26" aria-hidden="true" tabindex="-1"></a><span class="in">Reflection URL: https://github.com/...</span></span>
<span id="cb18-27"><a href="#cb18-27" aria-hidden="true" tabindex="-1"></a><span class="in">My biggest takeaway: ...</span></span></code></pre></div>
<hr />
<h4 id="if-you-get-stuck-17">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I do not know what to write</td>
<td>Start with the simplest section: “What I would tell future
students.” One honest sentence is enough.</td>
</tr>
<tr>
<td>My Markdown formatting looks wrong</td>
<td>Check that headings have a space after the <code>#</code> and that
blank lines separate paragraphs.</td>
</tr>
<tr>
<td>I want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-bonus-b.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="bonus-c-create-a-group-challenge">Bonus C: Create a Group
Challenge</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/bonus-c-group-challenge.yml">bonus-c-group-challenge.yml</a></p>
<p><strong>For students who:</strong> Want to design exercises for
future cohorts.</p>
<p><strong>What you will do:</strong> Design a collaborative challenge
that 3-5 students could work on together, then document it in the
learning-room.</p>
<p><strong>When this unlocks:</strong> Bonus challenges unlock after
Challenge 15. You can pick this as soon as that challenge closes.</p>
<p>### Step-by-step</p>
<h4 id="step-1-choose-a-collaboration-problem">Step 1: Choose a
collaboration problem</h4>
<ol type="1">
<li>Think of a task that requires collaboration – something one person
cannot easily do alone.</li>
<li>Aim for a challenge that teaches teamwork, not just parallel solo
work.</li>
</ol>
<h4 id="step-2-create-your-challenge-file">Step 2: Create your challenge
file</h4>
<ol type="1">
<li>Create
<code>docs/group-challenges/YOUR-USERNAME-challenge.md</code></li>
<li>Add a clear title and short summary at the top</li>
</ol>
<h4 id="step-3-include-the-required-sections">Step 3: Include the
required sections</h4>
<p>Your challenge design must include: - <strong>Title</strong> – a
catchy, descriptive name - <strong>Goal</strong> – what students will
learn or accomplish - <strong>Team size</strong> – how many people
(recommend 3-5) - <strong>Time estimate</strong> – how long it should
take - <strong>Instructions</strong> – step-by-step guide -
<strong>Success criteria</strong> – how do students know they are done?
- <strong>Accessibility note</strong> – how does this work for all
participants regardless of how they interact with technology?</p>
<h4 id="step-4-commit-and-share">Step 4: Commit and share</h4>
<ol type="1">
<li>Commit your file</li>
<li>Push your branch</li>
<li>Open a PR</li>
</ol>
<h4 id="design-criteria">Design criteria</h4>
<p>Strong group challenges: - Require genuine collaboration (not just
dividing work) - Have clear success criteria - Are accessible to all
participants - Can be completed within the workshop timeframe</p>
<hr />
<p><strong>Your evidence</strong> (fill in when closing this issue):</p>
<pre class="text"><code>Challenge name: ...
What teams would do: ...
File URL: https://github.com/...</code></pre>
<hr />
<h4 id="if-you-get-stuck-18">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I cannot think of a group challenge</td>
<td>Look at the bonus challenges in CHALLENGES.md for inspiration. Think
about a real problem your team could solve together.</td>
</tr>
<tr>
<td>I want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-bonus-c.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="bonus-d-notification-mastery">Bonus D: Notification Mastery</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/bonus-d-notifications.yml">bonus-d-notifications.yml</a></p>
<p><strong>For students who:</strong> Want to practice inbox management
and notification configuration.</p>
<p><strong>Chapter:</strong> <a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/10-notifications-and-day-1-close.md">Ch10:
Notifications and Day 1 Close</a></p>
<p><strong>What you will do:</strong> Configure your GitHub notification
settings for a productive workflow, then demonstrate your setup.</p>
<p><strong>When this unlocks:</strong> Bonus challenges unlock after
Challenge 15. You can use this one anytime after that point.</p>
<h4 id="notification-configuration-checklist">Notification configuration
checklist</h4>
<p>Go to <a
href="https://github.com/settings/notifications">github.com/settings/notifications</a>
and configure:</p>
<ul>
<li><strong>Email notifications:</strong> Choose which events trigger
emails</li>
<li><strong>Web notifications:</strong> Configure the notification inbox
on GitHub.com</li>
<li><strong>Watching:</strong> Review which repositories you are
watching and adjust</li>
<li><strong>Custom routing:</strong> If you have multiple email
addresses, set up routing rules</li>
<li><strong>GitHub Mobile:</strong> If you use the mobile app, configure
push notification preferences</li>
</ul>
<h4 id="demonstrate-your-setup">Demonstrate your setup</h4>
<p>After configuring, answer these questions: 1. How will you know when
someone requests your review? 2. How will you avoid being overwhelmed by
notifications from busy repositories? 3. What is your strategy for the
GitHub notification inbox (read all, triage, filter)?</p>
<hr />
<p><strong>Your evidence</strong> (fill in when closing this issue):</p>
<pre class="text"><code>My notification strategy: ...
I configured email for: ...
I am watching ___ repositories because: ...
I will avoid notification overload by: ...</code></pre>
<hr />
<h4 id="if-you-get-stuck-19">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>I cannot find notification settings</td>
<td>Go to github.com, select your profile picture (top-right), select
Settings, then Notifications in the left sidebar.</td>
</tr>
<tr>
<td>There are too many options</td>
<td>Start with the defaults and change one thing at a time. The most
important setting is whether you get emails for PR review requests.</td>
</tr>
<tr>
<td>I want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-bonus-d.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<hr />
<h3 id="bonus-e-explore-git-history-visually">Bonus E: Explore Git
History Visually</h3>
<p>Source template: <a
href="learning-room/.github/ISSUE_TEMPLATE/bonus-e-git-history.yml">bonus-e-git-history.yml</a></p>
<p><strong>For students who:</strong> Want to see branching and merging
as a visual timeline.</p>
<p><strong>What you will do:</strong> Use GitHub Desktop (or the
GitHub.com commit graph) to explore the learning-room’s Git history as a
visual timeline.</p>
<p><strong>When this unlocks:</strong> Bonus challenges unlock after
Challenge 15. You can choose this one without waiting for Challenge
16.</p>
<h4 id="instructions-5">Instructions</h4>
<h4 id="using-github-desktop">Using GitHub Desktop:</h4>
<ol type="1">
<li>Open the learning-room repository in GitHub Desktop.</li>
<li>Go to the <strong>History</strong> tab.</li>
<li>Explore the commit timeline. Notice:
<ul>
<li>How branches appear as parallel lines</li>
<li>Where merges bring lines back together</li>
<li>Which commits are yours vs seeded peer-simulation commits</li>
</ul></li>
</ol>
<h4 id="using-github.com-alternative">Using GitHub.com
(alternative):</h4>
<ol type="1">
<li>Go to the learning-room repository on GitHub.com.</li>
<li>Select <strong>Insights</strong> &gt; <strong>Network</strong> to
see the branch graph.</li>
<li>Or select <strong>Commits</strong> on the Code tab to see the linear
history.</li>
</ol>
<h4 id="what-to-observe">What to observe</h4>
<p>Answer these questions as you explore: - How many branches exist in
the repository right now? - Can you find your Challenge 5 commit in the
history? - Where does your <code>learn/YOUR-USERNAME</code> branch
diverge from <code>main</code>? - Can you find the merge commit from
your Challenge 9 PR? - What is the oldest commit in the repository?</p>
<hr />
<p><strong>Your evidence</strong> (fill in when closing this issue):</p>
<pre class="text"><code>Tool I used: GitHub Desktop / GitHub.com
Number of branches I found: ...
My commit from Challenge 5: ...
The oldest commit in the repo: ...
Something surprising I noticed: ...</code></pre>
<hr />
<h4 id="if-you-get-stuck-20">If you get stuck</h4>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Symptom</th>
<th>Try this</th>
</tr>
</thead>
<tbody>
<tr>
<td>GitHub Desktop does not show all branches</td>
<td>Fetch from the remote first (Repository &gt; Fetch origin) to get
the latest branches.</td>
</tr>
<tr>
<td>The network graph on GitHub.com is hard to read</td>
<td>The graph can be complex with many contributors. Try zooming in on a
specific time period.</td>
</tr>
<tr>
<td>I cannot find my commits</td>
<td>Search for your username in the commit history, or filter by
branch.</td>
</tr>
<tr>
<td>I want to check my work</td>
<td><a
href="https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-bonus-e.md">View
the reference solution</a></td>
</tr>
</tbody>
</table>
<h2 id="authoritative-sources">Authoritative Sources</h2>
<p>Use these official references when you need the current source of
truth for the Git and GitHub workflow concepts summarized in this
generated walkthrough.</p>
<ul>
<li><a href="https://docs.github.com/en">GitHub Docs, home</a></li>
<li><a href="https://github.blog/changelog/">GitHub Changelog</a></li>
<li><a
href="https://docs.github.com/en/get-started/using-git/about-git">About
Git</a></li>
<li><a
href="https://docs.github.com/en/get-started/using-github/github-flow">GitHub
flow</a></li>
<li><a
href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests">About
pull requests</a></li>
<li><a
href="https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues">About
issues</a></li>
<li><a
href="https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project">Contributing
to a project</a></li>
</ul>
<h3 id="section-level-source-map">Section-Level Source Map</h3>
<ul>
<li><strong>Core challenges:</strong> <a
href="https://docs.github.com/en">GitHub Docs, home</a> <a
href="https://github.blog/changelog/">GitHub Changelog</a> <a
href="https://docs.github.com/en/get-started/using-git/about-git">About
Git</a> <a
href="https://docs.github.com/en/get-started/using-github/github-flow">GitHub
flow</a> <a
href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests">About
pull requests</a> <a
href="https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues">About
issues</a> <a
href="https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project">Contributing
to a project</a></li>
<li><strong>Bonus challenges:</strong> <a
href="https://docs.github.com/en">GitHub Docs, home</a> <a
href="https://github.blog/changelog/">GitHub Changelog</a> <a
href="https://docs.github.com/en/get-started/using-git/about-git">About
Git</a> <a
href="https://docs.github.com/en/get-started/using-github/github-flow">GitHub
flow</a> <a
href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-references">About
pull requests</a> <a
href="https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues">About
issues</a> <a
href="https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project">Contributing
to a project</a></li>
</ul>