adding gh actions for promq tests if alerts directory is modified (#741)

.github/workflows/test-alerts.yaml

@@ -0,0 +1,31 @@
+name: Alerts Promql tests
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - examples/alerts/**
+  pull_request:
+    branches:
+      - main
+    paths:  
+      - 'examples/alerts/**'
+jobs:
+  promql-tests:
+    name: Promql Unit tests
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        shell: bash
+    steps:
+      - name: Set up Go 1.21.x
+        uses: actions/setup-go@v4
+        with:
+          go-version: 1.21.x
+        id: go
+      - name: Check out code
+        uses: actions/checkout@v4
+      - name: Run Promql tests
+        run: |
+            make test-alerts

examples/alerts/README.md

@@ -37,5 +37,7 @@ make sloth-generate
 There are also two matching unit tests to verify and test the alerts that Sloth has generated. These can be run using the make target:
 
 ```
-make alerts-tests
+make test-alerts
 ```
+
+Note: The prometheus unit tests will also run via Github actions when a change is made in the alerts file.

make/alerts.mk

@@ -21,7 +21,7 @@ container-runtime-tool:
                                             exit 1; \
                                         fi))
 
-alerts-tests: container-runtime-tool ## Test alerts using promtool 
+test-alerts: container-runtime-tool ## Test alerts using promtool 
 	$(CONTAINER_RUNTIME_BIN) run --rm -t \
 	-v $(AVAILABILITY_SLO_RULES):/prometheus/slo-availability.yaml \
 	-v $(LATENCY_SLO_RULES):/prometheus/slo-latency.yaml \