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>
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