docs(challenge-06): clarify PR titles are scoped to a single challenge#253
Merged
Conversation
support#64 (DebeeArmstrong): Challenge 6 tells students to write any descriptive PR title, but Challenge 7's automatically-opened practice PR has a fixed title chosen by the automation. Nothing said these are unrelated, so a reader could think a specific title carries across challenges. Add a one-line note that titles only apply to that PR and some later challenges (like 7) open their own separate, auto-titled PR. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
Peer Review AssignedHi @accesswatch! Your PR has been automatically paired with @taylorarndt for peer review. For @taylorarndt:This is a great opportunity to practice code review skills! Here's what to look for: Content Quality:
Accessibility:
Documentation:
Review Guidelines:
Resources: Pairing by Learning Room Grouping Engine |
There was a problem hiding this comment.
Pull request overview
Clarifies for learners in Chapter 6 that the pull request title they choose is only relevant to that single PR, and that later challenges (notably Chapter 7) may open their own automation-titled PRs. This reduces confusion when moving between challenge workflows that create separate PRs.
Changes:
- Add a short “Note” in Challenge 6.2 explaining PR titles don’t carry across challenges.
- Regenerate the corresponding HTML output for Chapter 6.
- Update the generated site search index to reflect the rebuilt HTML set.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/06-working-with-pull-requests.md | Adds the learner-facing clarification note in Challenge 6.2. |
| html/docs/06-working-with-pull-requests.html | Regenerated HTML output including the new note. |
| html/search-index.json | Regenerated search index as part of the HTML rebuild outputs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test plan
npm run build:htmlnpm run validate:authoritative-sources🤖 Generated with Claude Code