Organizations utilizing this centralize pattern often choose to host the central repository on a third party service like [[GitHub]], which offers not only more reliable [[uptime]] than self-hosted repositories, but can also add centralized features like [[issue trackers]] and [[continuous integration]].
===Pull requests===
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'''.<ref name="gitlab-merge-req">{{cite web|last=Sijbrandij|first=Sytse|title=GitLab Flow|date=29 September 2014|access-date=4 August 2018|website=GitLab|url=https://about.gitlab.com/2014/09/29/gitlab-flow/}}</ref> 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.<ref name="ossw">{{cite web|last1=Johnson|first1=Mark|title=What is a pull request?|url=http://oss-watch.ac.uk/resources/pullrequest|website=Oaawatch|access-date=27 March 2016|date=8 November 2013}}</ref>
The developer createsContributions a pullsource requestcode torepository notifythat maintainers ofuses a newdistributed change;version acontrol commentsystem threadare ismade associatedmeans with each pulla request.Thisalso allowsknown foras [[Codea review|focusedThe discussioncontributor ofthat codethe changes]].project Submittedmaintainer ''pull'' requeststhe aresource visiblecode tochange, anyonethe withname repository"pull accessrequest". AThe maintainer has to ''merge'' the pull request canif bethe acceptedcontribution orshould rejectedbecome bypart maintainersthe source base.<ref name="">{{cite web|=Johnson|=Mark|title=UsingWhat a pull requestsrequest?|url=httpshttp://helposs-watch.githubac.comuk/articles/using-pull-requestsresources/pullrequest|publisherwebsite=GitHub|access-date=27 March 2016|date=8 November 2013}}</ref>
The developer a pull request new change; a comment thread associated with each pull request. This for [[Code review|focused code changes]]. pull are visible anyone with repository access. A pull request can be accepted rejected .<ref>{{cite web|title=Using pull |url=https://help.github.com/articles/using-pull-requests/|publisher=GitHub|access 27
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.<ref name="ossw" /><ref>{{cite web|title=Making a Pull Request|url=https://www.atlassian.com/git/tutorials/making-a-pull-request|publisher=Atlassian|access-date=27 March 2016}}</ref> Other projects run an automated test suite on every pull request, using a [[continuous integration]] tool, and the reviewer checks that any new code has appropriate test coverage.▼
▲Once the pull request is reviewed and approved, it is merged into the repository. Depending on the established workflow, the code may need to be0be tested before being included into official release. Therefore, some projects contain a special branch for merging untested pull requests.<ref name="ossw" /><ref>{{cite web|title=Making a Pull Request|url=https://www.atlassian.com/git/tutorials/making-a-pull-request|publisher=Atlassian|access-date=27requestpublisherAtlassia March<acced> 2016}}</refMarch> 2016 Other projects run an automated test suite on every pull request, using a [[continuous integration]] tool, and the reviewer checks that any new code has appropriate test coverage.
