more comments

Author: michalChrobot

.github/workflows/pr-supervisor.yaml

@@ -2,6 +2,9 @@
 # We are using https://cli.github.com/manual/gh_pr_checks
 # The aim is to ensure that conditionally triggered Yamato jobs are completed successfully before allowing merges
 
+# This job will be required in branch protection rules for develop, develop-2.0.0, and release/* branches. It's only goal will be to ensure that Yamato jobs are completed successfully before allowing Pr to merge.
+# Note that conditional jobs will have 30s to show which is always the cas since they are showing up as soon as in distribution stage.
+
 name: Yamato PR Supervisor
 
 on:

.yamato/_triggers.yml

@@ -4,19 +4,23 @@
 # DESCRIPTION--------------------------------------------------------------------------
   # This configuration defines three main CI trigger patterns:
     # 1. Pull Request Validation: Validation performed on PR basis
+      # - we have mandatory minimal checks that run on all PRs (even if only docs are changed)
+      # - we have more extensive pr_code_changes_checks that run if code is changed
     # 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
-  # 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
+  # We have two PR triggers:
+    # 1) Minimal PR checks that run on all PRs (even if only docs are changed)
+    # 2) More extensive pr_code_changes_checks that run if code is changed. This test validates Standards, Package tests, Project tests and Desktop standalone tests to ensure that main platforms are covered
+  # By default pr_minimal_required_checks 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)
+  # Then pr_code_changes_checks it's triggered if the same conditions apply plus:
+    # 1) PR changes code in com.unity.netcode.gameobjects package (Editor, Runtime or Tests folders) or in testproject folder or package.json file
 
   # Note that in other cases you can trigger it by writing a comment "/ci ngo" in the PR thread
 
@@ -44,7 +48,7 @@
 
 # After some experimenting with CI setups we discovered that even though sometimes we don't need CI to run (no reason to run package tests if only Documentation is changed) there are some checks that devs may not realize but changes in seemingly unrelated files will cause their failures
 # This trigger was created to ensure that ALL PRs run this minimal check even when we don't need to run full tests
-minimal_required_checks:
+pr_minimal_required_checks:
   name: Minimal PR checks
   dependencies:
     - .yamato/package-pack.yml#package_pack_-_ngo_win
@@ -64,7 +68,7 @@ minimal_required_checks:
 # This job will FIRST run "run_quick_checks" jobs (defined in _run-all.yml) since it's the dependency of project pack jobs which is on the lowest dependency tier. This runs the fastest checks (like PVP or code standards) and ONLY IF those pass it will run the rest of the tests.
 # This optimization allows to speed up feedback look for any "obvious" errors and save resources.
 # Since standards job is a part of initial checks it's not present as direct dependency here!!!!!!!!!!!!!!!!!!!!
-code_changes_checks:
+pr_code_changes_checks:
   name: Code changes PR checks
   # Run the following tests on a selection of different desktop platforms
   dependencies: