Remove old CI

Author: noelsaw1

.github/workflows/README.md

@@ -64,6 +64,14 @@
 - NOT triggered by events in this repository
 - This is OK to keep as it's not causing duplicate runs
 
+### `example-caller.yml` - Template/Example File
+
+**Purpose:** Documentation and example for plugin developers
+- Shows how to use the reusable workflow in other repos
+- **DISABLED in this repo** - only triggers on `workflow_dispatch` (manual)
+- When copying to your plugin, uncomment the real triggers
+- This is OK to keep as it won't run automatically
+
 ## How to Modify CI Behavior
 
 ### Adding a New Check

.github/workflows/example-caller.yml

@@ -1,16 +1,34 @@
 # Example: How to call the reusable WP Performance workflow from your plugin
-# Version: 1.0.0
+# Version: 1.0.1
 #
+# ⚠️  THIS IS AN EXAMPLE/TEMPLATE FILE - NOT AN ACTIVE WORKFLOW
+#
+# This file is for DOCUMENTATION purposes only.
 # Copy this file to your plugin's .github/workflows/ directory and customize.
 # Rename to something like "ci.yml" or "performance.yml"
+#
+# DO NOT activate this workflow in the wp-code-check repository itself!
+# The active workflow for this repo is ci.yml
 
-name: CI - Performance Checks
+name: CI - Performance Checks (EXAMPLE - DO NOT USE)
 
+# TRIGGERS DISABLED - This is a template file that will never run automatically
+# When using in your own plugin, replace the 'on:' section below with real triggers
 on:
-  push:
-    branches: [main, development]
-  pull_request:
-    branches: [main]
+  workflow_dispatch:  # Only manual trigger - prevents automatic runs
+    inputs:
+      note:
+        description: 'This is a template file. Copy to your plugin repo to use.'
+        required: false
+        default: 'See README for usage instructions'
+
+# EXAMPLE TRIGGERS (uncomment and customize when using in your plugin):
+#
+# on:
+#   push:
+#     branches: [main, development]
+#   pull_request:
+#     branches: [main]
 
 jobs:
   # Option 1: Call the reusable workflow from the central repo

CHANGELOG.md

@@ -68,10 +68,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     - `.github/workflows/performance-audit-slack-on-failure.yml`
   - **Safeguards Added**:
     - Added prominent warning comments in `ci.yml` header explaining single-workflow policy
+    - Disabled `example-caller.yml` triggers (changed to `workflow_dispatch` only)
+      - This template file was causing duplicate CI runs
+      - Now only runs manually, preventing automatic triggers
+      - Added clear warnings that it's a template/example file
     - Created `.github/workflows/README.md` documenting:
       - Why we use a single workflow
       - How to modify CI behavior without creating new files
       - Checklist before creating new workflows
+      - Documentation of template files (example-caller.yml, wp-performance.yml)
       - History of consolidation to prevent regression
 
 - **DRY Refactor: Consolidated Grouping Logic** - Created centralized `group_and_add_finding()` helper function