A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2018-January/151911.html below:

[Python-Dev] GH-NNNN vs #NNNN in merge commit

[Python-Dev] GH-NNNN vs #NNNN in merge commit [Python-Dev] GH-NNNN vs #NNNN in merge commitBerker Peksağ berker.peksag at gmail.com
Thu Jan 25 16:22:51 EST 2018
On Thu, Jan 25, 2018 at 11:50 PM, Terry Reedy <tjreedy at udel.edu> wrote:
> On 1/25/2018 1:03 PM, Mariatta Wijaya wrote:
>
>> One idea is maybe have a bot to do the squash commit, for example by
>> commenting on GitHub:
>> @merge-bot merge <commit title> <commit message>
>
>
>> So core devs can do the above instead of pressing the commit button. Any
>> thoughts on this?
>
>
> I can hardly believe that you are seriously proposing that I should replace
> a click with a 16 char prefix and then retype the title and message.  Did I
> misunderstand?

If I understand Mariatta correctly, you can just left a "@merge-bot
merge" comment if you're happy with the commit message. Then the bot
itself can replace #NNNN with GH-NNNN, clean the body of the commit
message from commits like "* fix typo", squash commits, and merge.

--Berker
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4