# GitHub Pull Request merge commands

2 messages from 2015-06-16 to 2015-06-16. Participants: Florian Lindner, Johannes Löthberg.
Thread: https://gitlist.dev/t/39642

## Florian Lindner, 2015-06-16 08:55

Subject: GitHub Pull Request merge commands
Message-ID: <mloo9l$agl$6@ger.gmane.org>
URL: https://gitlist.dev/e/mloo9l%24agl%246%40ger.gmane.org

```
Hello,

GitHub proposes these commands to merge a pull requests (explanations from 
me, to make sure I got it correctly)

# Basically branch develop to davidsblom-develop
git checkout -b davidsblom-develop develop

# Pull in foreign repos commits from foreign develop branch.
git pull git://github.com/davidsblom/precice.git develop

# Edit and merge the changes to the main repos develop branch
git checkout develop
git merge --no-ff davidsblom-develop
git push origin develop

My question is, if davidsblom make further commits to his develop branch 
(after the pull request was issued) aren't these commits also included in 
the pull and therefore in the merge? If yes, isn't the idea to merge just 
the changes that the pull request was about? If not, why? ;-)

Thanks,
Florian

```

## Johannes Löthberg, 2015-06-16 09:33

Subject: Re: GitHub Pull Request merge commands
Message-ID: <20150616093345.GA28617@leeloo.kyriasis.com>
URL: https://gitlist.dev/e/20150616093345.GA28617%40leeloo.kyriasis.com
In-Reply-To: <mloo9l$agl$6@ger.gmane.org>

```
On 16/06, Florian Lindner wrote:
>My question is, if davidsblom make further commits to his develop branch
>(after the pull request was issued) aren't these commits also included in
>the pull and therefore in the merge? If yes, isn't the idea to merge just
>the changes that the pull request was about? If not, why? ;-)
>

A pull request is "about" all commits in the branch, which is why 
topic-branches should be used for PRs.

-- 
Sincerely,
  Johannes Löthberg
  PGP Key ID: 0x50FB9B273A9D0BB5
  https://theos.kyriasis.com/~kyrias/

```