Mariatta Wijaya mariatta.wijaya at gmail.com
Thu Jan 25 19:47:16 EST 2018

• Previous message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
• Next message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

I think we're starting to deviate from the original topic here which is:
please replace # with GH- when you click Squash & Merge button.

The idea of the mergebot (by issuing a command) was brought up for a
different purpose: to automate the merging of a PR after all CI passes
(which can take time) and an approval by a core dev.
I still like that idea, if we can figure out a way to supply a commit
message we really want, before the bot merges the PR. It might be a
separate discussion for core-workflow or python-committers?

In my mind, even if we have such mergebot implemented, core devs can still
merge using the UI if they want to.
(Remember to replace the # with GH-)


Mariatta Wijaya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20180125/366d0d3b/attachment.html>

---

• Previous message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
• Next message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list