Esmvaltool: Enable stickler-ci

[bjlittle]

Could we enable the stickler-ci service for the repo please.

This will perform automated lint and pep8 tests using flake8 and pep8 on all pull-requests. The service uses sensible defaults but is easily customisable, see here.

I don't have sufficient repo privileges to enable this service.

Ping owner @veyring

[bjlittle]

Ping @ESMValGroup/esmvaltool-developmentteam

[bjlittle]

No doubt we will need a .stickler.yml file to exclude and ignore the files and directories that require not to be checked.

This kinda forces the coversation forward with regards to sensibly restructuring the repo hierarchy for different source code i.e. R, Python and ncl @nielsdrost

[bjlittle]

@veyring also see http://mark-story.com/posts/view/introducing-stickler-ci for context

[markstory]

If you run into any issues getting stickler-ci going, let me know :smile:

[bjlittle]

Ping @axel-lauer, could you please enable stickler-ci for the repo.

It's easy. Login to stickler-ci using your github account, allow the site to access your github metadata, then simply check the tick box against the ESMValGroup/ESMValTool repo. Bosh. Job done! It'll be 30 seconds of your day well spent!

Then we get to leverage all the lovely stickler-ci lint and pep8 yummy goodness as a service on all pull-requests. What's not to like? Komm schon! :wink:

[bjlittle]

@axel-lauer if you do enable stickler-ci, could you please ping me or close this issue, then I can spin a .stickler.yml file. Thanks.

[axel-lauer]

I just enabled stickler-ci access. Have fun!