-
Notifications
You must be signed in to change notification settings - Fork 40
Description
When Bors does the merge of the PR, it only puts the description from the PR into its commit message on the merge commit. Importantly, it leaves out the original title, which I claim is a bug in Bors.
This bug matters because the workflow of github often leads one to put important info into the title of the PR and the title alone: When I create a PR via github (on the button that comes up when you've recently pushed to a branch on your fork of the repository), it extracts the title of the PR from the first line of the commit message (or some prefix of that first line), and then uses the rest of the commit message as the description, leaving out the first sentence itself.
Concrete example:
Consider this PR: rust-lang/rust#12154
Here is the commit that the title and description of that PR was based upon: pnkfelix/rust@d2d1129
But here is the merge commit that bors decided to create: rust-lang/rust@fd4979a
Notably, the first line of the original commit had the most important information about the commit, but it is missing from bors' merge.
Now, this is not a fatal bug, because:
- One can easily workaround it by copying the title into the description in the PR (or, if one prefers, formatting one's git commits with a title followed by a description that stands indpendently from the title).
- One can always follow the parents of the bors-merge in the commit graph to find the original commit's first line so no information has been lost.
But it would still be nice if Bors just copied the title into the commit message for the merge.