Opting for manual release trigger

Author: Vahila

.github/workflows/cd.yaml

@@ -17,13 +17,14 @@ on:
         # Note: Change this default to true,
         #       if the checkbox should be checked by default.
         default: false
+  ###### Opting for manual release trigger so commented check_run trigger
   # If you don't want any automatic trigger in general, then
   # the following check_run trigger lines should all be commented.
   # Note: Consider the use case #2 config for 'validate_only' below
   #       as an alternative option!
-  check_run:
-    types:
-      - completed
+  # check_run:
+  #   types:
+  #     - completed
 
 permissions:
   checks: read
@@ -33,6 +34,7 @@ jobs:
   maven-cd:
     uses: jenkins-infra/github-reusable-workflows/.github/workflows/maven-cd.yml@v1
     with:
+      ###### Opting for a manual release trigger so updated validate_only accordingly
       # Comment / uncomment the validate_only config appropriate to your preference:
       #
       # Use case #1 (automatic release):
@@ -41,14 +43,14 @@ jobs:
       #   - Perform a validation only run with drafting a release note,
       #     if manually triggered AND inputs.validate_only has been checked.
       #
-      validate_only: ${{ inputs.validate_only == true }}
+      # validate_only: ${{ inputs.validate_only == true }}
       #
       # Alternative use case #2 (no automatic release):
       #   - Same as use case #1 - but:
       #     - Let any check_run trigger a validate_only run.
       #       => enforce the release job to be skipped.
       #
-      #validate_only: ${{ inputs.validate_only == true || github.event_name == 'check_run' }}
+      validate_only: ${{ inputs.validate_only == true || github.event_name == 'check_run' }}
     secrets:
       MAVEN_USERNAME: ${{ secrets.MAVEN_USERNAME }}
       MAVEN_TOKEN: ${{ secrets.MAVEN_TOKEN }}