Removing the quality gate check as the official Sonar scan appears to do a quality gate check.

.gitea/workflows/build.yaml

@@ -5,10 +5,10 @@ on:
   pull_request:
       types: [opened, synchronize, reopened]
 
-name: SonarQube Scan
+name: Docker Scan, Lint, & Deploy via Compose
 jobs:
   sonarqube:
-    name: SonarQube Scanning & Status
+    name: SonarQube Scanning & Quality Gate
     runs-on: ubuntu-latest
     steps:
     - name: Checking out
@@ -17,17 +17,18 @@ jobs:
         fetch-depth: 0
 
     - name: SonarQube Scan
+      id: sonarqube-scan
       uses: SonarSource/sonarqube-scan-action@v4.0.0
       env:
         SONAR_HOST_URL: ${{ secrets.SONARQUBE_HOST }}
         SONAR_TOKEN: ${{ secrets.SONARQUBE_TOKEN }}
 
-    - name: SonarQube Quality Gate Check
-      id: quality-gate
-      uses: SonarSource/sonarqube-quality-gate-action@v1.1.0
-      env:
-        SONAR_HOST_URL: ${{ secrets.SONARQUBE_HOST }}
-        SONAR_TOKEN: ${{ secrets.SONARQUBE_TOKEN }}
+    # - name: SonarQube Quality Gate Check
+    #   id: quality-gate
+    #   uses: SonarSource/sonarqube-quality-gate-action@v1.1.0
+    #   env:
+    #     SONAR_HOST_URL: ${{ secrets.SONARQUBE_HOST }}
+    #     SONAR_TOKEN: ${{ secrets.SONARQUBE_TOKEN }}
 
   docker-compose-dry-run:
     name: Dry Run Docker Compose
@@ -74,7 +75,7 @@ jobs:
       
       - name: Merge PR with Tea CLI
         run: |
-          tea pr m "${{ gitea.ref }}"
+          tea pr m "${{ gitea.repository. }}"
 
       - name: Deploy Docker Compose Changes
         uses: astappiev/docker-compose-remote-action@master