-
Notifications
You must be signed in to change notification settings - Fork 6
solution 04 branch out
This shows how to create a branch from each tool. You only needed to use one.
- Go to the repository's Code tab
- Click the branch dropdown (it says "main")
- Type a new branch name like
fix/welcome-todo - Click "Create branch: fix/welcome-todo from main"
The branch now exists on GitHub. You can switch to it using the same dropdown.
git checkout -b fix/welcome-todo
Or use the Source Control sidebar: click the branch name in the bottom-left status bar, then select "Create new branch."
- Click the Current Branch dropdown
- Click "New Branch"
- Enter the name
fix/welcome-todo - Confirm it is based on
main
gh repo clone <workshop-org>/learning-room-<your-username>
cd learning-room
git checkout -b fix/welcome-todo
Good branch names are short and descriptive:
-
fix/welcome-todo-- fixing a TODO in welcome.md -
feature/add-schedule-link-- adding a new link -
docs/update-readme-- documentation change
All of these are valid. The convention type/description is common but not required.
The learning objective is understanding that branches let you work in isolation without affecting main. If you created any branch with any name, you completed this challenge.
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.
- On github.com: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- In VS Code (with Git): GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- In GitHub Desktop: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- With GitHub CLI: GitHub Docs, home, GitHub Changelog, GitHub Copilot docs, Custom instructions support matrix, About custom agents
- Branch naming: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- 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