Solution Reference: Challenge 1 -- Find Your Way Around
This is one way the scavenger hunt could look. Your exact findings will vary depending on when you completed the challenge. If you found the key elements, you succeeded.
Expected findings
Code tab
- The root of the repository contains files like
README.md,docs/, and.github/ - The file count varies as the repository evolves -- any reasonable count is correct
Issues tab
- You should have found at least one open issue
- If no issues were open, noting that the tab exists is sufficient
docs/welcome.md
- The first paragraph introduces the learning room and what students will do
- You may have noticed TODO comments -- those are intentionally left for Challenge 2
Repository description and README
- The description appears at the top of the Code tab, below the repository name
- The README renders automatically below the file list
Alternate approaches
- github.com: Click each tab in the top navigation bar
- github.dev: Press
.on any repo page to open the web editor, then use the Explorer sidebar - VS Code with GitHub extension: Use the GitHub Repositories extension to browse remotely
- GitHub CLI:
gh repo view Community-Access/git-going-with-github --webopens the repo in a browser
What matters
The learning objective is familiarity with repository navigation, not memorizing exact file counts. If you explored the tabs and found the key files, 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.
- Expected findings: GitHub Docs, home, GitHub Changelog
- Alternate approaches: GitHub Docs, home, GitHub Changelog
- What matters: GitHub Docs, home, GitHub Changelog