-
-
Notifications
You must be signed in to change notification settings - Fork 2
patchbot plugins
Patchbot plugins and migration to GitHub Actions
┌─┬──────┐
│░│ ⊙ ʘ │ .oO(where will I travel after retirement?)
│░│ │
│░│ ──── │
╘═╧══════╛
Developer's guide: Working on Tickets explains the new GH Actions workflows that replace the Patchbot.
Developer's guide: Additional development and testing tools has more details.
TBD
Build the html documentation.
This is mandatory. Any failure will prevent the ticket to be merged.
See definitions in src/.relint.yml
Look for some wrong patterns in python or rst files.
-
xrange -
.iterkeys, .itervalues, .iteritems -
basestring -
__nonzero__
These are not allowed in python 3. (TO BE REMOVED)
Look for some wrong patterns in cython files.
-
import sixandfrom six import
Never ever import anything from "six" in a Cython file.
Check that some python3 incompatible code does not appear. (TO BE REMOVED)
-
ifilter, imap, izip -
raise statements -
cmp(userichcmpfor comparison) -
<>(the correct syntax is!=) -
<type '[a-z]*'> -
next -
__metaclass__ -
except Exception, var -
apply -
sagenb(the legacy notebook is deprecated)
Check that some bad latex code does not appear.
This means \choose, \over, \atop, \above, \overwithdelims, \atopwithdelims, \abovewithdelims.
All these commands are obsolete in latex.
Perform various checks, mainly about blocks in the documentation.
-
correct syntax is
.. SEEALSO:: -
TESTSandEXAMPLESshould be plural, andNOTEsingular -
no
::afterINPUTandOUTPUTblocks, only a single colon -
no
::afterREFERENCEblocks, only a single colon -
no
:at the end of lines, namely the colon should not be preceded by a space -
no
Returnsat the start of lines, butReturnfor the first line (short summary) orThis returnsotherwise
Look for the presence of triple colons ::: or : ::
Check for the existence of a commit message for every commit.
Try to check that coverage did increase.
The coverage is the percent of functions that are doctested. This must be 100%.
Look for the presence of non-ascii characters in python and cython files.
This detects the presence of the encoding line at the top of files. (TO BE REMOVED)
Check that doctest continuation use the correct syntax, namely ....:
Check that new deprecations use the correct ticket number.
Run pyflakes on the modified .py files.
This typically reports about unused variables or imports, that you should remove.
This is tailor-made to understand lazy imports.
Sometimes it gives false-positive warnings.
Run pycodestyle on the modified .py files.
Currently, the selected options are W605, E401, E701, E702, E711, E712.
See pycodestyle documentation for more information.
Look for the presence of badly formatted trac roles :trac:
The correct syntax is :trac:23456``
Try to decide if the startup time is getting worse.
This performs a statistical analysis, which is not always pertinent.
Count modules imported at startup, and compare to stored data to see if this has increased.
Build the pdf documentation.
This is not activated by default on the patchbot clients.
The aim of this plugin is not clear.