GitHub Action to run cpplint on pushes & pull requests (#3)

* GitHub Action to run cpplint on pushes & pull requests

This is a much simpler solution that loads quickly but does not require a custom Dockerfile.

* Update README.md

* Delete dockerimage.yml

* Delete main.yml

* Delete Dockerfile

* Delete entrypoint.sh

* Update README.md

* Update cpplint.yml

Author: cclauss

.github/workflows/cpplint.yml

@@ -0,0 +1,13 @@
+# GitHub Action to run cpplint recursively on all pushes and pull requests
+# https://github.com/cpplint/GitHub-Action-for-cpplint
+
+name: cpplint
+on: [push, pull_request]
+jobs:
+  cpplint:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v1
+    - uses: actions/setup-python@v1
+    - run: pip install cpplint
+    - run: cpplint --recursive .

.github/workflows/dockerimage.yml

@@ -5,22 +5,18 @@ Each time that new code is pushed into your repo, you can have a [cpplint](https
 Example workflow:
 * Put the following text into a file named `.github/workflows/cpplint.yml` in your repo):
 ```yaml
-on: push
-name: on push
+name: cpplint
+on: [push, pull_request]
 jobs:
-  gitHubActionForCpplint:
-    name: GitHub Action for cpplint
+  cpplint:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@master
-    - name: GitHub Action for cpplint
-      uses: cpplint/GitHub-Action-for-cpplint@master
-      with:
-        args: cpplint --recursive .
+    - uses: actions/checkout@v1
+    - uses: actions/setup-python@v1
+    - run: pip install cpplint
+    - run: cpplint --recursive .
 ```
-
-Or to add other cpplint options to "__args =__" above.
-
+Customize the final line to match your requirements.
 ```
 Syntax: cpplint.py [--verbose=#] [--output=emacs|eclipse|vs7|junit]
                    [--filter=-x,+y,...]