https://python.coderdojohasselt.be/en/sessions/git/15-git-pull-requests/index.htmlYou built a feature on a branch. Good commit messages, tidy work. Now you want to get your code into master. You could do git merge and be done. But in a team that doesn’t work. Someone else has to look at your code first: check for mistakes, for style, for things you missed. That is a pull request. A pull request (PR) is a request: “Bring my changes in.” You open it on GitHub. Your teammates look at your code and give feedback. You change things. Only when everyone is happy does the code go to master.Hugoenhttps://python.coderdojohasselt.be/en/sessions/git/15-git-pull-requests/mentor-notes/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://python.coderdojohasselt.be/en/sessions/git/15-git-pull-requests/mentor-notes/index.htmlGoal of this session At the end of this session a ninja can: Work together with a buddy on the same GitHub repo (collaborator access). Push a feature branch to GitHub. Open a pull request with a structured description (what, why, how to test). Review a buddy’s PR: read the diff, give specific feedback on lines, approve or request changes. Handle feedback by pushing extra commits to the feature branch. Merge an approved PR and clean up the branch (locally and on GitHub). This is the last session of the Git series.