checks : I guess this is where I configure pylint checks, etc,. What is the list of checks I can use ?
The list of checkers is not handy to obtain, I admit. A quick way can bot to grep the apycotbot/checkers directory:
% grep -r "id =" checkers/chk* checkers/chks_debian.py: id = 'debian_lint' checkers/chks_debian.py: id = 'debian_piuparts' checkers/chks_debian.py: id = 'debian_dpkgdeb' checkers/chks_debian.py: id = 'ldi_upload' checkers/chks_html.py: id = 'html_tidy' checkers/chks_pkg.py: id = 'pkg_doc' checkers/chks_pkg.py: id = 'lgp_check' checkers/chks_pt.py: id = 'pt_syntax' checkers/chks_python.py: id = 'python_syntax' checkers/chks_python.py: id = 'python_unittest' checkers/chks_python.py: id = 'python_pytest' checkers/chks_python.py: id = 'python_lint' checkers/chks_python.py: id = 'python_test_coverage' checkers/chks_python.py: id = 'python_check' checkers/chks_rest.py: id = 'rest_syntax' checkers/chks_xml.py: id = 'xml_well_formed' checkers/chks_xml.py: id = 'xml_valid'
Note that lgp  and ldi  references two other projects of Logilab. Not sure you will be interested by these checks for now.
Concerning the python checkers (chks_python.py):
Another thing, you have to check the need_preprocessor attribute that determine a further entry point for the apycot configuration.
The available options for each check are not documented and you need to look into code to discover them :-( Then, checks can be configured later in the config field (see the configuration field explanation below).
No real API exists, only the _run() method which is responsible of returning check status.
In the same manner of the checkers:
% grep -r "id =" preprocessors/pp\* preprocessors/pp_buildeb.py: id = 'lgp_build' preprocessors/pp_make.py: id = 'make' preprocessors/pp_setup.py: id = 'set_python_env' preprocessors/pp_setup.py: id = 'setup_install' preprocessors/pp_zope_install.py: id = 'zope_install'
Basically, you will only need to use the setup_install preprocessor. In this case, you must add the following line in the 'preprocessor' field of your apycot configuration:
> What is the difference between an apycot config and an apycot group ? > The configuration parameters looks exactly the same.
Historically, we had only apycot config to set a test config for one project. But the duplicates of configuration are so frequent that it's handy to include several apycot group config in project config by using the relation 'use group' (think generic tests).
We have a lot to do to clarify attributes from the legacy version of Apycot. Here is a brief comment about the tedious ones:
Hope it will help,