-
Notifications
You must be signed in to change notification settings - Fork 6
solution 05 make your mark
github-actions[bot] edited this page May 14, 2026
·
2 revisions
This shows an example edit and commit. Your changes will be different.
File: docs/welcome.md
Before (line 15):
<!-- TODO: add link to workshop schedule -->After:
See the [workshop schedule](https://github.com/Community-Access/git-going-with-github/blob/main/admin/DAY1_AGENDA.md) for session times.docs: replace TODO with workshop schedule link
Resolves the placeholder on line 15 of welcome.md by adding
a link to the schedule file.
- First line: Short summary (50 characters or less is ideal), starts with the type of change
- Blank line: Separates summary from body
- Body (optional): Explains what changed and why
Fix TODO in welcome.md
Add schedule link to welcome page
Both are clear and descriptive. The more structured format is a convention, not a requirement.
- github.com: Click the pencil icon on the file, make the edit, fill in the commit message at the bottom
-
github.dev: Press
.to open the editor, edit the file, use the Source Control sidebar to commit -
VS Code: Edit locally, stage with
git add, commit withgit commit - GitHub Desktop: Edit in your preferred editor, return to Desktop, write the message, click Commit
The learning objective is making a meaningful change and describing it in a commit message. Any clear edit with any descriptive message is a success.
Use these official references when you need the current source of truth for facts in this chapter.
Use this map to verify facts for each major section in this file.
- Example edit: GitHub Docs, home, GitHub Changelog
- Example commit message: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- Alternate approaches: GitHub Docs, home, GitHub Changelog
- What matters: GitHub Docs, home, GitHub Changelog
- 00 Setup
- 01 Tools
- 02 GitHub
- 03 Repositories
- 04 Learning Room
- 05 Issues
- 06 Pull Requests
- 07 Merge Conflicts
- 08 Culture
- 09 Labels Milestones Projects
- 10 Day 1 Close
- 11 VS Code Interface
- 12 VS Code Accessibility
- 13 How Git Works
- 14 Git in Practice
- 15 Code Review
- 16 Copilot
- 17 Issue Templates
- 18 Fork and Contribute
- 19 Accessibility Agents
- 20 Build Your Agent
- 21 GitHub Accessibility and Open Source
- 22 What Comes Next
Use these official references when you need the current source of truth for the wiki navigation structure and the GitHub workflow concepts represented by these links.
- Start: GitHub Docs, home, GitHub Changelog
- Day 1: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- Day 2: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- Reference: GitHub Docs, home, GitHub Changelog
- Contributors: GitHub Docs, home, GitHub Changelog