fix: PR should not be scanned by sonar

Author: John Doe

.github/workflows/test.yaml

@@ -24,9 +24,10 @@ jobs:
 
             - name: SonarCloud Scan
               uses: sonarsource/sonarcloud-github-action@master
+              if: github.ref == 'refs/heads/main'
               env:
-                GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-                SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
+                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+                  SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
 
             - uses: actions/upload-artifact@v3
               with:
@@ -52,6 +53,7 @@ jobs:
     release-docker:
         runs-on: ubuntu-20.04
         needs: ["test-and-build"]
+        if: contains(github.ref, 'refs/tags/') || github.ref == 'refs/heads/main'
         steps:
             - name: Checkout
               uses: actions/checkout@v2

README.md

@@ -19,7 +19,7 @@ Simply clone your scripts repository in your pod workspace, execute script and e
 ### Git clone inside CI job
 
 `git-clone-operator checkout` is a CLI command that could be a replacement of `git clone` and `git checkout`. 
-It's advantage is that it is designed to be running automatic: When repository does not exists, it gets cloned, when exists, then updated with remote.
+Its advantage is that it is designed to be running automatic: When repository does not exist, it gets cloned, when exists, then updated with remote.
 
 
 Setting up
@@ -147,7 +147,7 @@ Roadmap
 
 ### v3
 
-- [ ] Possibly: Reacting on webhooks from Gitea and GitHub to update revision on existing pods (using `kind: Job` with cloned volume definitions from `kind: Pod`, using the same configuration as initContainer)
+- [ ] Possibly: Reacting on webhooks from Gitea and GitHub to update revision on existing pods - deleting marked pods maybe?
 
 Thanks
 ------