sympy-bot
sympy-bot copied to clipboard
sympy
GitHub bot for SymPy
In addition to the release notes, we can do some basic linting of the PR description. These wouldn't be things that would fail the build, but would hopefully guide people...
The author and PR number are added automatically, so we should error if the person adds them.
I don't know if this is feasible, however, I would still like the sympy-bot to tag the PRs with labels, at least related to the module mentioned in the release...
The release notes may look better if instead of formatting it like * core * change 1 * change 2 * solvers * change 1 * change 2 ```md *...
I just edited the release notes a bit and noted that some "second level lists" were using `-`and some `*`. I manually edited all to use `*`, but it would...
See https://github.com/sympy/sympy/pull/9294. A new PR had all the commits from it and was merged. The PR was old and didn't have release notes, resulting in an error from the bot.
See https://github.com/sympy/sympy/pull/15917. The ` ` got added to the release notes.
https://github.com/sympy/sympy/wiki/Release-Notes-for-1.4/_history There seem to be double entries for sympy/sympy#16063, sympy/sympy#15816, sympy/sympy#16028...
The following error happened with PR https://github.com/sympy/sympy/pull/15814. ``` 2019-01-20T17:09:31.684311+00:00 app[web.1]: PR #15814 was opened. 2019-01-20T17:09:31.738566+00:00 app[web.1]: Error handling request 2019-01-20T17:09:31.738574+00:00 app[web.1]: Traceback (most recent call last): 2019-01-20T17:09:31.738595+00:00 app[web.1]: File "/app/.heroku/python/lib/python3.6/site-packages/aiohttp/web_protocol.py",...
Right now if there is an error (for example, an invalid use of the API), it just raises an exception and doesn't post anything, except for a few code paths...