git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GitHub Pull Request merge commands

From
Johannes Löthberg <johannes@kyriasis.com>
Date
Jun 16, 2015, 09:33 UTC
Message-ID
<20150616093345.GA28617@leeloo.kyriasis.com>
In-Reply-To
<mloo9l$agl$6@ger.gmane.org>
On 16/06, Florian Lindner wrote:
Show 5 quoted lines
>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/
Previous: Florian Lindner
Message 2 of 2 in “GitHub Pull Request merge commands”
  1. Florian LindnerJun 16, 2015
  2. Johannes LöthbergJun 16, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.