Added possibility of usage of /ci ngo

Author: michalChrobot

.yamato/_triggers.yml

@@ -2,40 +2,42 @@
 ---
 
 # DESCRIPTION--------------------------------------------------------------------------
-# This configuration defines three main CI trigger patterns:
-# 1. Pull Request Validation: Validation performed on PR basis
-# 2. Nightly Development: Test set run nightly (validates most important test cases)
-# 3. Weekly Full Validation: Test set run weekly (validates all test cases to prevent any surprises)
-# Each pattern represents different balance between validation depth, execution time and CI resource usage
+  # This configuration defines three main CI trigger patterns:
+    # 1. Pull Request Validation: Validation performed on PR basis
+    # 2. Nightly Development: Test set run nightly (validates most important test cases)
+    # 3. Weekly Full Validation: Test set run weekly (validates all test cases to prevent any surprises)
+  # Each pattern represents different balance between validation depth, execution time and CI resource usage
 
 # TRIGGER PATTERNS-------------------------------------------------------------------
 
 # Pull Request:
-# This test validates Standards, Package tests, Project tests and Desktop standalone tests to ensure that main platforms are covered
-# Triggers on PRs to develop, develop, and release branches
-# Focuses on critical validation paths that we should validate before merging PRs
-# Cancels previous runs on new commits
-# Excludes draft PRs
-# Excludes running when changes are not touching package or testproject code (e.g. docs only changes)
+  # This test validates Standards, Package tests, Project tests and Desktop standalone tests to ensure that main platforms are covered
+  # Focuses on critical validation paths that we should validate before merging PRs. It also cancels previous runs on new commits
+  # By default it's triggered if
+    # 1) PR targets develop, develop-2.0.0 or release branches
+    # 2) PR is not a draft
+    # 3) PR changes files in package or testproject folders (doesn't run on for example DOCS only changes)
+
+  # Note that in other cases you can trigger it by writing a comment "/ci ngo" in the PR thread
 
 # Nightly:
-# This test validates same subset as pull_request_trigger with addition of mobile/console tests and webgl builds
-# Runs daily on develop (local configuration)
-# Includes all test types but only on trunk.
-# Adds platform-specific and APV validation
+  # This test validates same subset as pull_request_trigger with addition of mobile/console tests and webgl builds
+  # Runs daily on develop (local configuration)
+  # Includes all test types but only on trunk.
+  # Adds platform-specific and APV validation
 
 # Weekly:
-# This test validates same subset as develop_nightly but runs per all supported editors as well as executes code coverage test and runs project standards per project
-# Runs across all supported editor versions
-# Includes code coverage analysis
-# Validates all projects and standards
+  # This test validates same subset as develop_nightly but runs per all supported editors as well as executes code coverage test and runs project standards per project
+  # Runs across all supported editor versions
+  # Includes code coverage analysis
+  # Validates all projects and standards
 
 # CONFIGURATION STRUCTURE--------------------------------------------------------------
-# Jobs configurations are generated by ensuring that all dependencies are successful.
-# The dependencies are taken from _run-all.yml file where we can gather multiple tests into proper sets
+  # Jobs configurations are generated by ensuring that all dependencies are successful.
+  # The dependencies are taken from _run-all.yml file where we can gather multiple tests into proper sets
 
 # QUALITY CONSIDERATIONS---------------------------------------------------------------
-# It's important to ensure that all dependencies exist (this can be verified in Yamato) since a modification in parameters may result in a given job not being generated, and thus we will not be able to run such erroneous job.
+  # It's important to ensure that all dependencies exist (this can be verified in Yamato) since a modification in parameters may result in a given job not being generated, and thus we will not be able to run such erroneous job.
 
 
 #-----------------------------------------------------------------------------------
@@ -67,12 +69,13 @@ pull_request_trigger:
     # TODO: consider setting up and running tests from Examples/
     # TODO: or docs only changes are spelling/link check
     expression: |-
-      (pull_request.target eq "develop" OR
+      pull_request.comment eq "ngo" OR
+      ((pull_request.target eq "develop" OR
       pull_request.target eq "develop-2.0.0" OR
       pull_request.target match "release/*") AND
       NOT pull_request.draft AND
       (pull_request.changes.any match "com.unity.netcode.gameobjects/**" OR
-      pull_request.changes.any match "testproject/**")
+      pull_request.changes.any match "testproject/**"))
     cancel_old_ci: true
 
 # Run all tests on trunk on nightly basis.