liveBook · Manning

Pull request

As explained in 100 SQL Server Mistakes and How to Avoid Them

A pull request is a proposal to review changes from one repository branch and merge them into another branch.

A pull request proposes reviewing changes from one repository branch before merging them into another, such as the trunk. The practical mistake is treating a remote-branch push as the merge itself: pushing changes displays a link for creating the request, while a repository contributor still reviews and merges the changes. section 7.6.1

Use this workflow when changes need review:

  • Save the changed artifact, stage it in the Git Changes window, add a commit comment, and commit the staged change. section 7.6.1
  • Push the commit to the remote branch with the up-arrow button. section 7.6.1
  • Follow the Create Pull Request link to GitHub, then request contributor review and merging into the trunk. section 7.6.1

How 100 SQL Server Mistakes and How to Avoid Them covers it

How deep it goes
Explains the Git-to-GitHub workflow from commit and push through review and merge, while deferring deeper Git and GitHub topics.
Examples
Uses the Git Changes window, a remote branch, the Create Pull Request link, and a changed CalculateCampaignSummary procedure.
What it assumes
Assumes basic repository and branch handling, while demonstrating staging, committing, pushing, and opening a GitHub request.
What you can do after
Apply it via GitHub to request contributor review before merging a remote-branch change into the trunk.
How it connects
Connects Git, GitHub, branches, repositories, code review, commits, and merging.

Also explained in

Compare how 6 books explain pull request →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of 100 SQL Server Mistakes and How to Avoid Them. The section links point to the parts of the book it draws on.