TechWorld with Nana on YouTube · Open on YouTube
Professional practice · Competent · Lesson 34 of 98 · 32 min video, then about 4 hours of practice
Working in a shared repository: branches and pull requests
After this you can work on a branch, open a focused pull request with a clear description, respond to review, and resolve a merge conflict.
Why it matters
On a team, every change goes through a pull request. A good one is small, does one thing, has a description that says what changed and why, and makes the reviewer's job easy. A large, unfocused pull request is a burden on your colleagues no matter how good the code is. Learn the branch-PR-review-merge loop, how to keep a branch up to date, and how to resolve conflicts calmly. Trap: 1,000-line pull requests. Split them. Google's guide on small changes explains why better than anyone.
How to use this resource
The common team workflows and when each one fits.
Go further
Go deeper