Peer review and inline comments
The cool thing about pull requests is that you have a nice and clear view of what is about to get merged. You can see only the changes that matter, and the best part is that you can fire up a discussion concerning those changes.
In the previous section, we submitted the pull request so that it can be reviewed and eventually get merged. Suppose that we are collaborating with a team and they chime in to discuss the changes. Let's first check the layout of a pull request.
The layout of a pull request
Every pull request pretty much looks as follows:
From the previous screenshot, you can tell what the specific number of the pull request is. It is like an identifier within the repository and it is not separated from the issues count. Issues and pull requests share the same ID counter. So, in the preceding example, you can see that although this is our first pull request, it is numbered #6; the previous five were issues:
Then, there is the information that the pull request...
