Challenge: Sign the Wall¶
Optional. No steps. Your call.
Every session ends with a challenge like this one. It uses the same skills as the session's exercise, on a problem these pages do not walk you through. Nobody expects you to finish it in the session. Work on it at home, with a teammate, or not at all. If you get stuck, open a hint. The hints point; they do not solve.
🎯 The goal¶
The team keeps a repository called the wall: gryphoncommand/wall. Every programmer signs it once. Your signature is one Markdown file, in the folder for this season, named after your GitHub username. Someone has already signed it. Match what they did.
Then do the one thing today's exercise did not do: ask for your branch to be merged. Mentors review every signature before it goes on the wall.
✅ Done when¶
- A file named after your GitHub username exists in this season's folder, on a branch you pushed to the wall repository.
- It has your name, your callsign (your GitHub username), and one appropriate line about you. Something your grandmother and your future employer could both read.
- There is a pull request asking to merge your branch into
main, and a mentor can see it. - Street cred: your file uses some Markdown formatting, and it looks right in the preview on GitHub.
🧰 What you already know that helps¶
- Everything in Your First Codespace and Your First Commit works the same in any repository.
- The file you made in
team/today is written in Markdown, and so is the one on the wall. - GitHub shows you a preview of a Markdown file when you click it, and there is a Preview tab when you edit one in VS Code.
Hint 1: where to start
Open the wall repository on GitHub and click into the folders. Which folder is this season's? What is the one file in it named? Open it and read it. Your file goes next to it, with the same shape.
Hint 2: the branch, the commit, the push
A Codespace works for any repository that has the green Code button. So does the pencil icon on any file on GitHub, if you would rather skip the Codespace: GitHub can create a branch and a commit for you from the web page. Either way, the branch is yours, the commit message says what it does, and the push puts it on GitHub.
Hint 3: the part nobody taught you
After you push a branch, GitHub often shows a yellow banner with a green button on the repository's page. Read what the button says. The Session 1 Reference git vocabulary table has a row for it. GitHub's own docs explain it in two minutes: search for "creating a pull request".
Hint 4: Markdown
Markdown is plain text with a few symbols that mean "make this a heading" or "make this bold". The file you are copying uses some of them. GitHub's guide is called "Basic writing and formatting syntax". Ten minutes there is enough for a lifetime of README files.