Professional workflow
How engineers actually use git
⏱ Est. ~2 min
01 · Read
You've learned all the git commands. Here's how professional engineers combine them every day:
💡 Picture thisA professional git workflow is like a team relay race. Each runner (engineer) takes the baton (pulls the latest code), runs their leg (works on a branch), passes the baton (pushes and opens a PR), and only swaps after the coach (reviewer) approves.
Key points
- 1. Fetch the latest changes: git pull
- 2. Create a branch: git checkout -b feature-name
- 3. Write code, test it
- 4. Stage changes: git add .
- 5. Commit: git commit -m "description"
- 6. Push to GitHub: git push
- 7. Open a Pull Request on GitHub
- 8. Team reviews, then merges
02 · Read
Commit messages matter. Future you (and your teammates) will read them. Good commit messages explain what changed and why, not just "changed something."
Key points
- Bad: 'fixed stuff', 'changes', 'asdf'
- Good: 'Fix login button not responding on mobile'
- Good: 'Add search feature to product list'
- Good: 'Update API endpoint for user authentication'
03 · Quiz
When starting a new feature, what's the first thing you should do?
- Create a new branch
- Start editing files immediately
- Delete the old code
- Push to main
Other lessons in this chapter
⚠ The full interactive experience needs JavaScript. Please enable it and reload.
※ This is an independent Traditional Chinese teaching project — not an official Anthropic product. Claude™ is a trademark of Anthropic, PBC.