ci: stop adding PR builds as releases in Sentry (#2701)

as this clutters the monitoring and makes it confusing to use "Resolved in the next release"
Aam-Digital · Dec 4, 2024 · 1debe1d · 1debe1d
1 parent 46077c5
commit 1debe1d
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/.github/workflows/pull-request-update-or-push-tag.yml b/.github/workflows/pull-request-update-or-push-tag.yml
@@ -146,12 +146,12 @@ jobs:
           - linux/arm64
         os:
           - ubuntu-latest
-          - [self-hosted, Linux, ARM64]
+          - [ self-hosted, Linux, ARM64 ]
         exclude:
           - platform: linux/arm64
             os: ubuntu-latest
           - platform: linux/amd64
-            os: [self-hosted, Linux, ARM64]
+            os: [ self-hosted, Linux, ARM64 ]
     runs-on: ${{ matrix.os }}
     steps:
       - name: Checkout repository files
@@ -360,6 +360,7 @@ jobs:
           npm install -g @sentry/cli
 
       - name: Create Release
+        if: ${{ github.event.ref != '' }} # only send "official" releases to Sentry
         run: |
           sentry-cli releases new "ndb-core@${{ env.TAG }}"