Solution Reference: Challenge 9 -- Merge Day

This shows what a successful Day 1 completion looks like.

What happens at merge

When your PR from Challenge 6 (or a later challenge) is approved and merged:

  1. The "Merge pull request" button turns green
  2. After clicking it, your branch's commits appear on main
  3. The linked issue (from Closes #N) automatically closes
  4. The PR status changes to "Merged" with a purple icon

Example evidence

Your Day 1 recap evidence might include:

What I merged: PR #5 which fixed the TODO in welcome.md (linked to issue #3)

What I learned today:

  • Repositories have a navigable structure with tabs for code, issues, and PRs
  • Issues document problems; PRs propose solutions
  • Branches let you work without affecting main
  • Merge conflicts happen when two people change the same lines -- they are normal and fixable
  • Open source projects have community guidelines that shape how people collaborate

What surprised me: How much of open source is communication (issues, PR descriptions, comments) rather than just writing code.

Alternate approaches

  • Post your recap as a comment on your challenge issue
  • Share a summary in the workshop discussion channel
  • Write a short reflection in a new file on your branch

What matters

The learning objective is completing the Day 1 loop: issue to branch to commit to PR to merge. If you merged at least one PR and can articulate what you learned, you completed this challenge.

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.