docs: Improve readme

- removes false claim that the binary needs to be in same folder as git repository
- adds example usage with Github actions

Closes #93

README.md

@@ -14,7 +14,22 @@ Tool to make sure your commits are compliant with [conventional commits](https:/
 
 Commitsar is shipped as a Dockerfile. This is the easiest way to add it to your CI.
 
-**Important: Commitsar currently needs to be in the same folder as the git repository you want checked**
+**Important: Commitsar currently needs to be run in the same folder as the git repository you want checked, currently no override is provided for setting path to git repo see https://github.com/commitsar-app/commitsar/issues/93**
+
+#### Github action
+
+Checkout git in order to get commits and master branch
+```
+- name: Check out code into the Go module directory
+        uses: actions/checkout@v1
+```
+
+Run the Commitsar action
+```
+- name: Commitsar Action
+  uses: commitsar-app/[email protected] (substitute for current version)
+```
+
 
 ##### Example for CircleCI:
 

www/content/index.md

@@ -11,7 +11,23 @@ Tool to make sure your commits are compliant with [conventional commits](https:/
 
 Commitsar is shipped as a Dockerfile. This is the easiest way to add it to your CI.
 
-**Important: Commitsar currently needs to be in the same folder as the git repository you want checked**
+**Important: Commitsar currently needs to be run in the same folder as the git repository you want checked, currently no override is provided for setting path to git repo see https://github.com/commitsar-app/commitsar/issues/93**
+
+#### Github action
+
+> Github actions
+
+Checkout git in order to get commits and master branch
+```
+- name: Check out code into the Go module directory
+        uses: actions/checkout@v1
+```
+
+Run the Commitsar action
+```
+- name: Commitsar Action
+  uses: commitsar-app/[email protected] (substitute for current version)
+```
 
 ## Example for CircleCI