-
Notifications
You must be signed in to change notification settings - Fork 6
solution 10 go local
github-actions[bot] edited this page May 14, 2026
·
2 revisions
This shows the local Git workflow from clone through push.
# Clone the repository
git clone https://github.com/<workshop-org>/learning-room-<your-username>.git
cd learning-room
# Create a branch
git checkout -b fix/local-edit
# Make an edit (any text editor works)
# For example, fix a typo or add content to docs/welcome.md
# Stage the change
git add docs/welcome.md
# Commit with a descriptive message
git commit -m "docs: fix typo in welcome page"
# Push the branch to GitHub
git push -u origin fix/local-edit- Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P)
- Run "Git: Clone" and paste the repository URL
- Open the cloned folder
- Click the branch name in the bottom-left status bar, create a new branch
- Edit a file
- Open the Source Control sidebar (Ctrl+Shift+G)
- Stage changes with the + icon, type a commit message, click the checkmark
- Click "Publish Branch" or use the sync button
- File, Clone Repository, paste the URL
- Current Branch dropdown, New Branch
- Open the file in your editor and make a change
- Return to GitHub Desktop -- it shows the diff
- Write a commit message at the bottom-left, click "Commit"
- Click "Publish branch" to push
After pushing, go to github.com and you should see:
- A banner saying "fix/local-edit had recent pushes" with a "Compare & pull request" button
- Your branch in the branch dropdown
- Your commit in the branch's commit history
The learning objective is executing the full local workflow: clone, branch, edit, commit, push. The specific change you made does not matter. If your branch appeared on GitHub with your commit, you succeeded.
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.
- Terminal/CLI approach: GitHub Docs, home, GitHub Changelog, GitHub Copilot docs, Custom instructions support matrix, About custom agents
- VS Code approach: GitHub Docs, home, GitHub Changelog
- GitHub Desktop approach: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- Verifying success: 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