Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use pylint as part of git branch pull requests #579

Open
3 tasks
Chris-Schnaufer opened this issue May 16, 2019 · 0 comments
Open
3 tasks

Use pylint as part of git branch pull requests #579

Chris-Schnaufer opened this issue May 16, 2019 · 0 comments

Comments

@Chris-Schnaufer
Copy link

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant