-
Notifications
You must be signed in to change notification settings - Fork 11
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
pylint git action #550
Comments
Try to setup pylint so that it will fail if more errors are added to the code base. i.e. set minium pass level. also look into pre-commit hooks |
I have established a 'pylint.yml' configuration file to automate pylint checks on the github actions. After running pylint, the resulting code quality score is compared to the value stored in the '.pylint-score' file. If the newly calculated score exceeds the value stored in the file, the test will pass. Subsequently, the value in the '.pylint-score' file is updated. This ensures that any new code additions maintain or improve upon the existing code quality score. |
Reminder to add in diagram to coast site of new github action work flow |
@thogar-computer , mermaid diagram added to the coast-site: |
Create a GitAction to run pylint test.
This would help with keeping the code readable and all that.
Currently a problem because there are too many fails. (Probably mostly from missing doc strings)
The text was updated successfully, but these errors were encountered: