Repository navigation
Git going workshop challenges 6-7 confusing documentation #64
Description
Source application
Git Going with Github
Feedback type
Bug report
Version or build
unclear
Platform
Windows 11 JAWS
Short summary
Challengs 6 and 7 have a conflict in their instructions.
What happened
In challenge 6:
- Activate the Create pull request button. It sits between the branch choosers and the diff, and the title and description fields do not appear until
you activate it. With a screen reader, use the button quick navigation key (B in NVDA and JAWS browse mode) or search the page for "Create pull request".- Write a descriptive PR title.
But in challenge 7 steps read:
Your practice PR: Look for a comment below (it may take a minute to appear) linking a pull request titled "Challenge 7 practice: resolve this merge conflict."
Work in that PR for this challenge -- not any other pull request you may already have open.
Step 1: Look at your practice PR
- Open the practice PR linked in a comment on this issue (titled "Challenge 7 practice: resolve this merge conflict")
- You should see a message: "Can't automatically merge" or "This branch has conflicts..."
Maybe this is why I had trouble with challenge 7. I did not create a PR with the title of "Challenge 7 practice: resolve this merge conflict"
I created my own title as suggested in challenge 6.
And there was no practice PR linked to in challenge 7 anyway.
So the docs imply that exact title needed to be used for the PR to work properly in the learning room.
This is not a support request, just general feedback on what to me were somewhat confusing sets of instructions.
Reproduction steps
Not relevant as this is not a support request.
Diagnostics or extra context
No response
Activity
github-actions commentedon Jul 6, 2026
Thanks for opening this request. A maintainer will review it within 24 to 48 hours.
accesswatch commentedon Jul 6, 2026
Thanks for the detailed writeup - this is genuinely useful feedback.
Two things worth separating here:
The underlying automation gap you likely hit (no practice PR ever appearing for Challenge 7) was a real bug, already fixed on 2026-07-05 in response to your earlier report (support#61). Challenge 7 now reliably opens its own dedicated practice PR titled "Challenge 7 practice: resolve this merge conflict" as soon as the Challenge 7 issue is created, with a comment linking it.
The documentation gap you're describing here - Challenge 6 telling you to pick any descriptive PR title, with nothing saying that choice is scoped to that one PR - was still real even after that fix. Fixed in docs(challenge-06): clarify PR titles are scoped to a single challenge git-going-with-github#253: Challenge 6 now has a note that its title guidance only applies to that PR, and that some later challenges (like 7) open their own separate, automatically-titled PR you don't need to match or reuse a title for.
Closing this out - thanks again for flagging it.