update example

Author: jippi

.gitlab-ci.yml

@@ -1,7 +1,18 @@
-scm-engine::evaluate:
+# NOTE: This is integration testing file, its not meant for production usage
+#       The README has a production example
+
+scm-engine::evaluate::on-change:
   image: ${CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX}/golang:1.22.3
   rules:
     - if: $CI_PIPELINE_SOURCE == 'merge_request_event'
   script:
     - go mod tidy
     - go run ./cmd/scm-engine/ evaluate
+
+scm-engine::evaluate::on-schedule:
+  image: ${CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX}/golang:1.22.3
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "schedule"
+  script:
+    - go mod tidy
+    - go run ./cmd/scm-engine/ evaluate all

README.md

@@ -119,12 +119,19 @@ Using scm-engine within a GitLab CI pipeline is straight forward.
 1. Setup a CI job using the `scm-engine` Docker image that will run when a pipeline is created from a Merge Request Event.
 
     ```yaml
-    scm-engine:
+    scm-engine::evaluate::on-merge-request-event:
       image: ghcr.io/jippi/scm-engine:latest
       rules:
         - if: $CI_PIPELINE_SOURCE == 'merge_request_event'
       script:
         - scm-engine evaluate
+
+    scm-engine::evaluate::on-schedule:
+      image: ghcr.io/jippi/scm-engine:latest
+      rules:
+        - if: $CI_PIPELINE_SOURCE == "schedule"
+      script:
+        - scm-engine evaluate all
     ```
 
 1. Done! Every Merge Request change should now re-run scm-engine and apply your label rules