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.

Sign up for GitHub

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

Jump to bottom

Introduce CI linter #26

Open
aleksslitvinovs opened this issue Dec 15, 2021 · 1 comment
Open

Introduce CI linter #26

aleksslitvinovs opened this issue Dec 15, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@aleksslitvinovs
Copy link
Collaborator

Py-TestUI code is quite inconsistent and I think enforcing consistent code guidelines is quite beneficial.

I am suggesting adding a CI job for every commit to run some kind of Python linter, e.g., Pylint. This would also require defining what code style (black, autopep8, isort, YAPF) is used in the code.
@aleksslitvinovs aleksslitvinovs added the enhancement New feature or request label Dec 15, 2021
@alvarolaserna
Copy link
Contributor

this is in progress already

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alvarolaserna @aleksslitvinovs