Assignment 2: You Can Build This

Welcome back -- or welcome for the first time! Day 2 moves from the browser to your local machine and introduces real-world development workflows.

Joining Day 2 Without Day 1?

You do not need to have attended Day 1 to succeed today. If you already have GitHub fundamentals (navigating repos, filing issues, opening PRs, reviewing code), you have the same foundation as Day 1 participants.

Before starting the challenges below, verify your readiness with the Day 2 Quick Start guide. It takes about 30 minutes and confirms you have the accounts, tools, and skills needed.

What You Will Do Today

During the live Day 2 core path, you will move from browser-based GitHub to local contribution work in VS Code. Some advanced challenges are intentionally available as stretch or async follow-up so participants and remote cohorts can continue at a sustainable pace.

  • Clone a repository and work with Git locally
  • Push a branch and open a PR from your local machine
  • Review a classmate's code and give constructive feedback
  • Use GitHub Copilot as a collaborative tool
  • Create or review a custom issue template, if time allows
  • Fork a real repository and prepare a cross-repo contribution path
  • Explore accessibility agents and how they work
  • Start your own capstone idea for Accessibility Agents, GLOW, or another repository, with a path to finish asynchronously

Challenges

Complete these challenges in order through Challenge 15. After Challenge 15, Challenge 16 and all five bonus challenges are available, so students can choose the capstone path, bonus work, or both during lab time or after the event.

Challenge What You Do Chapter
10. Go Local Clone, branch, edit, commit, and push using local Git Chapter 14
11. Open a Day 2 PR Open a PR from your locally-pushed branch Chapter 15
12. Review Like a Pro Review a classmate's PR with specific, constructive feedback Chapter 15
13. AI as Your Copilot Use Copilot to improve documentation and evaluate its output Chapter 16
14. Template Remix Create a custom YAML issue template Chapter 17
15. Meet the Agents Explore and run agents from the accessibility-agents repo Chapter 19
16. Capstone Project Prepare an impactful agentic contribution with responsibilities, guardrails, and review evidence Chapter 20

Automated Checks

Challenges 10, 14, and 16 have automated checks that run as GitHub Actions inside your repo:

  • Challenge 10: Verifies at least one commit exists on a non-default branch
  • Challenge 14: Verifies your YAML template has required name and description fields
  • Challenge 16: Verifies an Accessibility Agents agent file when you use that path; facilitators review GLOW or other-project evidence using the same mission, responsibilities, and guardrails criteria

Each check posts a single comment on the relevant pull request and updates it whenever you push a new change. If a check fails, read the comment and push an update.

After Challenge 15

Once Challenge 15 is complete, students can move into Challenge 16, Bonus A-E, or any combination of those paths. Challenge 16 remains the capstone, but the bonus challenges are intentionally unlocked at the same time so students can choose what is most useful next.

Evidence

Each challenge has an issue template in the Learning Room. Open the matching issue, complete the challenge, and post your evidence as described in the issue. Challenges 10, 14, and 16 also have automated checks that post PR feedback when you push or open a pull request; use those bot comments as guidance, then keep your human evidence in the challenge issue.

If You Get Stuck

Every chapter has an "If You Get Stuck" section with specific troubleshooting steps. Start there.

The solutions directory has reference solutions for every challenge. These show annotated examples of what a completed challenge looks like.

Fork Workflow (Challenges 15-16)

For the capstone challenge, Accessibility Agents is the default repository, but GLOW or another meaningful project is also valid when your contribution would help that repository. For any fork-based path:

  1. Fork the repository to your account
  2. Clone your fork locally
  3. Create a branch for your work
  4. Open a PR from your fork back to the original

See Chapter 18 for the full fork workflow. If forking is new to you, Chapter 6: Working with Pull Requests covers the fundamentals.

Bonus Challenges

If you finish early, check the Challenges page for bonus challenges.

Authoritative Sources

Use these official references when you need the current source of truth for facts in this chapter.

Section-Level Source Map

Use this map to verify facts for each major section in this file.