I have established a 'pylint_checking.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.
The current threshold was 5.0, but it was updated during this pull request to 5.58.
soutobias
commented
8 months ago
I have established a 'pylint_checking.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.
The current threshold was 5.0, but it was updated during this pull request to 5.58.