Ah yes, it works and I agree that it's OK in plain text. But we have careful if a contributor uses "\_" or something like that in a description. Maybe always edit to see the "source" of the description?
Victor Le jeu. 13 sept. 2018 à 16:54, Petr Viktorin <encu...@gmail.com> a écrit : > > > On Wed, Sep 12, 2018, 23:30 Victor Stinner <vstin...@redhat.com> wrote: > >> Today I created a PR with a description containing "type.__format__()". >> To display it properly, I chose to edit the description and write >> "type.\_\_format\_\_()". I guess that the bot will merge a description like >> that unchanged, right? So we should also be careful of description using >> Markdown syntax. >> > > Use `type.__format__`, with backticks, for code. That looks OK in plain > text. > Or edit before merging :) > > >> Victor >> >> Le mer. 12 sept. 2018 à 18:52, Mariatta Wijaya <mariatta.wij...@gmail.com> >> a écrit : >> >>> Update to the automerge bot: >>> >>> It will not merge unless there is "CLA signed" label, and no >>> "DO-NOT-MERGE" label. >>> >>> Again, please edit the PR title and description before adding the `🤖 >>> automerge` label. >>> The PR title and description will be used as the squashed commit message. >>> >>> Mariattaᐧ >>> ᐧ >>> _______________________________________________ >>> python-committers mailing list >>> python-committers@python.org >>> https://mail.python.org/mailman/listinfo/python-committers >>> Code of Conduct: https://www.python.org/psf/codeofconduct/ >>> >> _______________________________________________ >> python-committers mailing list >> python-committers@python.org >> https://mail.python.org/mailman/listinfo/python-committers >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> >
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
