Merge pull request #39 from viperior/feature/pylint-workflow-step

Move Pylint to GitHub Actions workflow

.github/workflows/build.yml

@@ -27,6 +27,9 @@ jobs:
         flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
         # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
         flake8 . --count --max-complexity=10 --max-line-length=100 --statistics
+    - name: Lint with pylint
+      run: |
+        python -m pylint ../python-project-template
     - name: Test with pytest (quick)
       run: |
         python -m pytest -v -x -n auto

.pylintrc

@@ -32,7 +32,7 @@ ignore-patterns=
 
 # Python code to execute, usually for sys.path manipulation such as
 # pygtk.require().
-init-hook=
+init-hook='import os, sys; sys.path.append(os.getcwd())'
 
 # Use multiple processes to speed up Pylint. Specifying 0 will auto-detect the
 # number of processors available to use.
@@ -85,7 +85,8 @@ disable=raw-checker-failed,
         suppressed-message,
         useless-suppression,
         deprecated-pragma,
-        use-symbolic-message-instead
+        use-symbolic-message-instead,
+        invalid-name
 
 # Enable the message, report, category or checker with the given id(s). You can
 # either give multiple identifier separated by comma (,) or put this option

CHANGELOG.md

@@ -6,6 +6,10 @@
 
 * Configure the `setuptools` build tool by creating the required metadata files
 
+### Improvements
+
+* Move pylint usage from the pytest test suite to a GitHub Actions workflow
+
 ## [0.7.0](https://github.com/viperior/python-project-template/tree/v0.7.0) (2022-02-26)
 
 ### Improvements