Step 1 of 12
GitHub pull requests for teams: what you'll practise
In this GitHub pull request tutorial for teams you practise the whole flow by doing it: branch, push, open a pull request, review it, fix it and merge it. You work on one change in a team's support tool, from the ticket to main, and see each step drawn as it happens.
Here is the whole story in seven moments. Press Play, or step through it.
In this lesson you'll:
- open a pull request with a title, a description and a closing keyword, as a draft first
- review a diff with line comments and pick Comment, Approve or Request changes
- answer a review with new commits and see why GitHub blocks a merge
- compare Create a merge commit, Squash and merge and Rebase and merge
It takes about 60 minutes. Each step ends with a "Try it" and one line to remember.
Takeaway: a pull request is a conversation about one change, and main only gets the change once the conversation is done.