# How the Pull Request is Built

DevFeed: [How the Pull Request is Built](<https://devfeed.tech/articles/how-the-pull-request-is-built-29358.md>)

Original publisher: [Read original article](<https://arturdryomov.dev/posts/how-the-pull-request-is-built/>)

Author: Artur Dryomov

Published: 2018-07-29T00:00:00Z

Content type: article

Language: en

Sources: [Artur Dryomov](<https://devfeed.tech/sources/artur-dryomov.md>)

Topics: [pull-requests](<https://devfeed.tech/topics/pull-requests.md>), [ci](<https://devfeed.tech/topics/ci.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Git](<https://devfeed.tech/topics/git.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [git](<https://devfeed.tech/tags/git.md>), [github](<https://devfeed.tech/tags/github.md>), [merge](<https://devfeed.tech/tags/merge.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>)

## AI overview

The article explains how continuous integration can build either a pull request's source branch or the result of merging it into the target branch. Using a color-resource example, it shows that building only the source branch can allow a pull request to merge while breaking the target branch, whereas building the merge result can detect the incompatibility. It also discusses rebasing source branches as an alternative.

## Source excerpt

Contact information of a friend of mine mentions that he doesn't have Facebook or Twitter accounts, but he is available at a really cool social network called... GitHub. Actually, GitHub is a social network, it even had direct private messages until April 2012. The developer community should be grateful to GitHub not only for awesome Octocats but for the popularizing a concept of pull requests. It is taken for granted now and we tend to forget that the closest thing before was sending a patch via email.