Pull Request (PR)

AKA: Merge Request (MR).
Context:
- It can (typically) result in another Software Developer to pull a branch from your repository into their repository.
- It can (typically) require: a Source Repository, a Source Branch, a Destination Repository, and a Destination Branch.
- It can range from being an Open MR, Approved MR, Merged MR, or Closed MR.
- It can be associated with a Pull Request-Related Metric, such as: Time to Merge, Pull Request Lead Time, Pull Request Size, Pull Request Flow Ratio, and Pull Requests Discussions [1].
- …
Example(s):
- …
Counter-Example(s):
- …
See: Code Branch, master Branch.

References

(Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/Distributed_version_control#Pull_requests Retrieved:2020-8-12.
- Contributions to a source code repository that uses a distributed version control system are commonly made by means of a pull request, also known as a merge request.^[1] The contributor requests that the project maintainer pull the source code change, hence the name "pull request". The maintainer has to merge the pull request if the contribution should become part of the source base.^[2]
  The developer creates a pull request to notify maintainers of a new change; a comment thread is associated with each pull request. This allows for focused discussion of code changes. Submitted pull requests are visible to anyone with repository access. A pull request can be accepted or rejected by maintainers.^[3]
  Once the pull request is reviewed and approved, it is merged into the repository. Depending on the established workflow, the code may need to be tested before being included into official release. Therefore, some projects contain a special branch for merging untested pull requests. ^[4] Other projects run an automated test suite on every pull request, using a continuous integration tool such as Travis CI, and the reviewer checks that any new code has appropriate test coverage.

https://github.com/community/community/discussions/27561
- QUOTE: ... Pull request is a confusing word and most people don't understand this concept, please change pull request into merge request or code merge request ...

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request
- QUOTE: ... In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. By default, any pull request can be merged at any time, unless the head branch is in conflict with the base branch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. ...

https://guides.github.com/activities/hello-world/#pr
- QUOTE: ... Pull Requests are the heart of collaboration on GitHub. When you open a pull request, you’re proposing your changes and requesting that someone review and pull in your contribution and merge them into their branch. Pull requests show diffs, or differences, of the content from both branches. The changes, additions, and subtractions are shown in green and red.
  As soon as you make a commit, you can open a pull request and start a discussion, even before the code is finished.
  By using GitHub’s mention system in your pull request message, you can ask for feedback from specific people or teams, whether they’re down the hall or 10 time zones away.
  You can even open pull requests in your own repository and merge them yourself. It’s a great way to learn the GitHub flow before working on larger projects.

https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-branches
- QUOTE: ... Use a branch to isolate development work without affecting other branches in the repository. Each repository has one default branch, and can have multiple other branches. You can merge a branch into another branch using a pull request.

https://www.atlassian.com/git/tutorials/making-a-pull-request
- QUOTE: ... In their simplest form, pull requests are a mechanism for a developer to notify team members that they have completed a feature. Once their feature branch is ready, the developer files a pull request via their Bitbucket account. This lets everybody involved know that they need to review the code and merge it into the master branch.
  But, the pull request is more than just a notification — it’s a dedicated forum for discussing the proposed feature. If there are any problems with the changes, teammates can post feedback in the pull request and even tweak the feature by pushing follow-up commits. All of this activity is tracked directly inside of the pull request. ...
  ... When you file a pull request, all you’re doing is requesting that another developer (e.g., the project maintainer) pulls a branch from your repository into their repository. This means that you need to provide 4 pieces of information to file a pull request: the source repository, the source branch, the destination repository, and the destination branch.