Don't use the PR body in the homu merge message#37
Conversation
This is not optimal, but worth discussing it. Probably we could be smarter and use a regexp to keep just the `Fixes|Closes|Adresses #xxx` messages. Fixes servo/servo#11153 Fixes #36
|
Since stripping the reviewable thing is easy, we could also do a servo-specific thing and look for the But that would assume the proper PR description is before that. |
|
Do we need to keep This patch seems OK to me, but all my uses of Homu are |
|
Yes, if it's in the commit description it will still close the issue, but some contributors add the |
|
For Rust I find this info super useful since I don't have to leave my terminal and can go through merge commits very fast. I've had to do this less in Servo (changes are more localized and easier to spot), but it's still useful. IMO stripping reviewable info might be better. Or make it configurable. |
|
Also, yeah, github doesn't close the issue otherwise |
|
The greetings at the very least should be removed from the commit message, IMO. |
|
@emilio, thanks for starting the discussion on this! It looks to me like the discussion here continued into #40 and reached a resolution that we should use custom tags within the PR template to tell Homu what content to leave out of the merge commit. It looks to me like this should be closed in favor of fixups on #40, but if I missed something in drawing that conclusion, you're more than welcome to reopen. |
|
Nope, thanks for closing this @edunham! :) |
This is not optimal, but worth discussing it.
Probably we could be smarter and use a regexp to keep just the
Fixes|Closes|Adresses #xxxmessages.Fixes servo/servo#11153
Fixes #36
This change is