Stage 2 · Lesson 7 of 8
Pull requests on GitHub
A asks to merge one into another on . It gives others a place to review the change before it lands. The flow is: create a branch, commit, push it, open the pull request, describe what changed and why, and ask for code review.
Clear help reviewers follow along. Reviewers comment on specific lines. You answer by pushing more commits to the same branch, and the pull request updates itself.
Once it is approved, it is merged and the branch is deleted. Keep each pull request to one change, small enough to review in about 15 minutes. Practise on your own repositories now, and read your own diff (the list of changes) before you merge. Almost every team and project works this way.
A question to check yourself, an AI practice session and 2 cheat sheet entries come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- CourseFreeThe Missing Semester of Your CS Education
MIT · Beginner
MIT lectures on dev tools; the shell, shell tools and version control lectures are enough
- GitHub repoFreeGitHub Skills: Introduction to GitHub
GitHub · Beginner
Free one-hour exercise: branch, commit, open and merge a pull request