terraref / computing-pipeline

Pipeline to Extract Plant Phenotypes from Reference Data
BSD 3-Clause "New" or "Revised" License
23 stars 13 forks source link

Use pylint as part of git branch pull requests #579

Open Chris-Schnaufer opened 5 years ago

Chris-Schnaufer commented 5 years ago

Define pylint configuration and make it part of pull request acceptance criteria

Tags: coding, standards, pull request, pylint, acceptance test

Description

Coding workflow change Right now there isn't a minimal coding standard to adhere to for python code. By leveraging TravisCI to perform a pylint test before running other tests, a minimal level of standards is enforced. An additional advantage is that some coding errors can be caught early on.

### Completion Criteria - [ ] Have a pylint configuration file available that submitted code can be tested against. - [ ] Integrate pylint checking to Pull Request acceptance criteria - [ ] Document the use of pylint as part of the Pull Request procedure