@htekdev/actions-debugger 1.0.131 → 1.0.132

package/errors/concurrency-timing/concurrency-timing-061.yml

@@ -0,0 +1,138 @@
+id: concurrency-timing-061
+title: '`github.workflow` in reusable workflow (`workflow_call`) returns caller''s name — shared concurrency group causes deadlock'
+category: concurrency-timing
+severity: error
+tags:
+  - concurrency
+  - reusable-workflow
+  - workflow-call
+  - github-workflow-context
+  - deadlock
+  - concurrency-group
+patterns:
+  - regex: 'Canceling since a deadlock for concurrency group .+ was detected between .+ and .+'
+    flags: 'i'
+  - regex: 'deadlock.*concurrency group.*detected'
+    flags: 'i'
+error_messages:
+  - "Canceling since a deadlock for concurrency group 'CI-refs/heads/main' was detected between 'CI workflow' and 'deploy'"
+  - "Canceling since a deadlock for concurrency group 'test-refs/heads/master' was detected between 'test workflow' and 'deploy'"
+root_cause: |
+  When a caller workflow invokes a reusable workflow via `uses:` (the `workflow_call` trigger),
+  the `github.workflow` context variable inside the CALLEE resolves to the CALLER's workflow
+  name — not the callee's own filename. This is documented behavior but it directly undermines
+  the widely recommended concurrency group pattern of `${{ github.workflow }}-${{ github.ref }}`.
+
+  If both the caller and the callee define:
+  ```yaml
+  concurrency:
+    group: ${{ github.workflow }}-${{ github.ref }}
+    cancel-in-progress: true
+  ```
+
+  Both workflows compute the SAME group key (because `github.workflow` is the caller's name in
+  both). GitHub detects that two workflow instances are competing for the same concurrency slot
+  in a way that cannot resolve — one is waiting for the other which is waiting for the first —
+  treats it as a deadlock, and cancels one of the runs.
+
+  **Why this is especially confusing:**
+  The fix recommended for general concurrency group collisions (`${{ github.workflow }}-${{ github.ref }}`)
+  is itself the cause of this deadlock when applied naively to reusable workflows. Teams that
+  copy the "safe" concurrency pattern from caller to callee introduce the bug.
+
+  **Real-world evidence:**
+  - actions/runner#3205: `github.workflow` returns parent workflow name in child workflows
+  - vergil-project/vergil-actions#176: ci-push.yml calls ci.yml via workflow_call; both use
+    `${{ github.workflow }}-${{ github.ref }}`; deadlock detected on every push
+  - github/gh-aw#35173: workflow_call fan-out cancellations due to shared concurrency namespace
+  - SO #78101326 (6 upvotes, 1738 views): "GitHub Actions concurrency deadlock" — 6 answers
+    confirming the root cause is `github.workflow` returning the caller name
+fix: |
+  Use `github.workflow_ref` instead of `github.workflow` in the CALLEE (reusable) workflow.
+  `github.workflow_ref` contains the full workflow file path (e.g.
+  `.github/workflows/deploy.yml@refs/heads/main`), which is unique per callee file and
+  does NOT inherit the caller's name.
+
+  **Preferred approach:** Define concurrency ONLY in the caller workflow and remove it from the
+  callee entirely. The callee runs as part of the caller's run and does not need its own
+  concurrency group. This is the cleanest fix and matches GitHub's recommendations for
+  reusable workflow design.
+
+  **Avoid:** Defining concurrency in both caller and callee with the same expression — this
+  is the root cause of the deadlock regardless of which context variable is used for the group
+  key, unless the keys are guaranteed to differ.
+fix_code:
+  - language: yaml
+    label: 'Callee (reusable workflow): use github.workflow_ref — unique per callee file'
+    code: |
+      # .github/workflows/deploy.yml (callee — reusable workflow)
+      name: Deploy
+
+      on:
+        workflow_call:
+
+      # ✅ github.workflow_ref includes the full path, NOT the caller's name
+      concurrency:
+        group: ${{ github.workflow_ref }}-${{ github.ref }}
+        cancel-in-progress: true
+
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - run: ./deploy.sh
+  - language: yaml
+    label: 'Preferred: define concurrency only in the caller, none in the callee'
+    code: |
+      # .github/workflows/ci.yml (caller workflow)
+      name: CI
+
+      on:
+        push:
+          branches: [main]
+
+      # Concurrency defined only in the caller
+      concurrency:
+        group: ${{ github.workflow }}-${{ github.ref }}
+        cancel-in-progress: true
+
+      jobs:
+        test:
+          runs-on: ubuntu-latest
+          steps:
+            - run: npm test
+
+        deploy:
+          needs: test
+          # ✅ No concurrency block here — the reusable workflow has no concurrency group
+          uses: ./.github/workflows/deploy.yml
+
+      ---
+      # .github/workflows/deploy.yml (callee — reusable workflow)
+      name: Deploy
+
+      on:
+        workflow_call:
+
+      # ✅ No concurrency block — inherit scheduling from caller
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - run: ./deploy.sh
+prevention:
+  - "Never use `github.workflow` in a reusable workflow's concurrency group — it resolves to the caller's name, not the callee's"
+  - "Use `github.workflow_ref` in callee workflows if a concurrency group is truly needed there"
+  - "Prefer defining concurrency only in the caller when calling reusable workflows via `uses:` — keep callee stateless"
+  - "Audit all reusable workflows for concurrency groups that use `github.workflow` and replace with `github.workflow_ref`"
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs'
+    label: 'GitHub Docs: Control the concurrency of workflows and jobs'
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#github-context'
+    label: 'GitHub Docs: github context — github.workflow_ref field'
+  - url: 'https://github.com/actions/runner/issues/3205'
+    label: 'actions/runner#3205: github.workflow returns parent name in child workflows (closed not_planned)'
+  - url: 'https://stackoverflow.com/questions/78101326/github-actions-concurrency-deadlock'
+    label: 'SO #78101326: GitHub Actions concurrency deadlock in reusable workflows (6 upvotes, 1738 views)'

package/errors/known-unsolved/known-unsolved-076.yml

@@ -0,0 +1,142 @@
+id: known-unsolved-076
+title: '`env` context unavailable in `strategy.matrix` — workflow env vars cannot be used in matrix definitions'
+category: known-unsolved
+severity: limitation
+tags:
+  - matrix
+  - env-context
+  - strategy
+  - fromJSON
+  - dynamic-matrix
+  - context-availability
+  - known-limitation
+patterns:
+  - regex: 'Error when evaluating .+strategy.+ for job'
+    flags: 'i'
+  - regex: 'strategy.*matrix.*\$\{\{.*env\.'
+    flags: 'i'
+  - regex: 'Unrecognized named-value: .+env.+ \(Line: \d+'
+    flags: 'i'
+error_messages:
+  - "Error when evaluating 'strategy' for job 'build'. .github/workflows/deploy.yaml (Line: 10, Col: 15): Error parsing fromJson"
+  - "Error when evaluating 'strategy' for job 'test'. Input string '3.11' is not a valid number. Path '[0]'"
+  - "Error when evaluating 'strategy' for job 'matrix-job': Object reference not set to an instance of an object"
+root_cause: |
+  The `env` context — workflow-level environment variables defined under the top-level `env:` key
+  — is NOT available during evaluation of `strategy.matrix`. GitHub Actions evaluates the
+  `strategy:` block at workflow QUEUING time, before jobs are dispatched and before environment
+  variable interpolation occurs. Any expression like `${{ env.VERSIONS_JSON }}` or
+  `${{ fromJSON(env.VERSIONS_JSON) }}` inside `strategy.matrix` resolves to an empty string
+  or produces a parse error.
+
+  **GitHub's documented context availability:**
+  Per the official context availability table, `env` is explicitly NOT listed as available in
+  `jobs.<job_id>.strategy`. Available contexts there are only: `github`, `inputs`, `vars`,
+  `needs`, `strategy`, and `matrix`.
+
+  **Common failure patterns:**
+  - Using `${{ fromJSON(env.MY_VERSIONS) }}` to share a JSON array between matrix and other steps
+  - Setting `env: DEPLOY_ENVS: '["staging","production"]'` at workflow level and referencing it
+    in the matrix include/exclude blocks
+  - Using workflow-level env vars to DRY up matrix configs shared with `run:` script logic
+
+  **Why this surprises developers:**
+  - `env` IS available inside `jobs.<job_id>.steps.*` — the limitation is specific to `strategy`
+  - The error message "Error parsing fromJson" doesn't mention that `env` context is unavailable
+  - The empty-string resolution (when no parse error) causes a silent empty matrix, not an error
+
+  Sources: actions/runner#480 (281 👍, open since 2020 — most-upvoted env context limitation);
+  SO#74072206 (10 upvotes, 19,053 views); SO#76039616 (6 upvotes, 10,482 views)
+fix: |
+  Three workarounds exist, in order of preference:
+
+  **Option 1 — Use `vars` context (org/repo-level variables)**
+  Org-level and repo-level variables (`vars.*`) ARE available in `strategy.matrix`.
+  Move shared values to repository Settings → Secrets and variables → Variables instead of
+  workflow-level `env:`.
+
+  **Option 2 — Compute matrix in a previous job's output (most flexible)**
+  Use a dedicated setup job that outputs the matrix JSON, then reference it in dependent
+  jobs via `fromJSON(needs.setup.outputs.matrix)`. This also enables dynamic matrix
+  generation from files, APIs, or scripts.
+
+  **Option 3 — Hardcode values directly in strategy.matrix**
+  Duplicate the values in `strategy.matrix` explicitly. Avoids the DRY violation but
+  is the simplest fix when values rarely change.
+fix_code:
+  - language: yaml
+    label: 'Option 1: Use vars context — repo/org variables ARE available in strategy'
+    code: |
+      # In repo Settings → Secrets and variables → Variables, create:
+      # Name: PYTHON_VERSIONS  Value: ["3.10","3.11","3.12"]
+
+      jobs:
+        test:
+          strategy:
+            matrix:
+              # ✅ vars context IS available in strategy.matrix
+              python-version: ${{ fromJSON(vars.PYTHON_VERSIONS) }}
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/setup-python@v5
+              with:
+                python-version: ${{ matrix.python-version }}
+            - run: python -m pytest
+  - language: yaml
+    label: 'Option 2: Compute matrix in a setup job, pass via needs outputs'
+    code: |
+      jobs:
+        setup:
+          runs-on: ubuntu-latest
+          outputs:
+            matrix: ${{ steps.set-matrix.outputs.matrix }}
+          steps:
+            - id: set-matrix
+              run: |
+                # Build matrix from any source: env var, file, API, conditional logic
+                echo 'matrix={"python-version":["3.10","3.11","3.12"]}' >> "$GITHUB_OUTPUT"
+
+        test:
+          needs: setup
+          strategy:
+            matrix:
+              # ✅ fromJSON(needs.*.outputs.*) IS available in strategy.matrix
+              ${{ fromJSON(needs.setup.outputs.matrix) }}
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/setup-python@v5
+              with:
+                python-version: ${{ matrix.python-version }}
+            - run: python -m pytest
+  - language: yaml
+    label: 'Anti-pattern: env context in strategy.matrix causes parse error'
+    code: |
+      # ❌ Workflow-level env vars are NOT available in strategy.matrix
+
+      env:
+        PYTHON_VERSIONS: '["3.10","3.11","3.12"]'
+
+      jobs:
+        test:
+          strategy:
+            matrix:
+              # This causes: "Error when evaluating 'strategy' for job 'test'"
+              python-version: ${{ fromJSON(env.PYTHON_VERSIONS) }}
+          runs-on: ubuntu-latest
+          steps:
+            - run: python --version
+prevention:
+  - "Use `vars.*` (repo/org variables from Settings) instead of workflow `env:` for values shared between matrix and steps"
+  - "Generate dynamic matrices in a dedicated setup job and pass via `needs.*.outputs.*`"
+  - "Consult the GitHub Actions context availability table before using any context in `strategy` — not all contexts are available there"
+  - "actionlint will flag `env` context usage in strategy blocks — add it to your CI pipeline or pre-commit hooks"
+  - "Remember: `env` IS available in `steps.*.run`, `steps.*.with`, and most other places — the restriction is specific to `strategy` and `concurrency`"
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#context-availability'
+    label: 'GitHub Docs: Context availability table (env not listed for strategy)'
+  - url: 'https://github.com/actions/runner/issues/480'
+    label: 'actions/runner#480: Workflow level env does not work in all fields (281 upvotes, open since 2020)'
+  - url: 'https://stackoverflow.com/questions/74072206/github-actions-use-variables-in-matrix-definition'
+    label: 'SO #74072206: Use variables in matrix definition (10 upvotes, 19,053 views)'
+  - url: 'https://stackoverflow.com/questions/76039616/how-to-read-in-an-array-of-strings-to-matrix-in-github-actions'
+    label: 'SO #76039616: Read array of strings into matrix (6 upvotes, 10,482 views)'

package/errors/silent-failures/silent-failures-121.yml

@@ -0,0 +1,140 @@
+id: silent-failures-121
+title: '`workflow_run: types: [completed]` triggers on ALL conclusions — deploy runs even when CI failed or was cancelled'
+category: silent-failures
+severity: silent-failure
+tags:
+  - workflow-run
+  - conclusion
+  - silent-failure
+  - deploy-on-failure
+  - ci-cd
+  - workflow-trigger
+  - conclusion-check
+patterns:
+  - regex: 'on:\s*\n\s+workflow_run:'
+    flags: 'im'
+  - regex: 'types:\s*[\[\s]*completed[\]\s]*\n'
+    flags: 'i'
+error_messages:
+  - "# No error message — the deploy workflow runs silently even when upstream CI failed or was cancelled"
+root_cause: |
+  The `workflow_run` event with `types: [completed]` fires whenever the referenced workflow
+  finishes — regardless of its conclusion. A completed workflow can have any of these conclusions:
+  `success`, `failure`, `cancelled`, `skipped`, `timed_out`, `action_required`, `neutral`,
+  or `stale`. GitHub fires `workflow_run: completed` for ALL of these states.
+
+  Developers commonly use `workflow_run` to chain a deploy or release workflow after a CI
+  workflow passes. The intuitive reading of "completed" is "finished successfully," but GitHub's
+  semantics are "finished with any outcome":
+
+  ```yaml
+  # ❌ This runs deploy even when CI failed, was cancelled, or was skipped
+  on:
+    workflow_run:
+      workflows: [CI]
+      types: [completed]
+  ```
+
+  Without an explicit `if:` conclusion check, the deploy workflow runs unconditionally after CI —
+  including when CI failed mid-run, was cancelled by a force-push, or was skipped by a path
+  filter. This silently deploys broken code (or publishes, releases, or notifies) whenever CI
+  does not succeed.
+
+  **Why this is a silent failure:**
+  - No error appears — the triggered workflow runs normally and reports "success"
+  - The CI failure and deploy completion appear as separate workflow runs — easy to miss
+  - GitHub does not add a default conclusion filter — the developer must add it manually
+  - The mistake is natural: "trigger when CI is done" sounds equivalent to "trigger when CI passes"
+
+  Sources: GitHub Docs (workflow_run event, conclusion field); SO#62750603 (159 upvotes,
+  152,034 views — top answer recommends adding conclusion check); `ahmadnassri/action-workflow-run-wait`
+  (39 stars — third-party action created specifically to work around this limitation)
+fix: |
+  Add an `if:` condition at the JOB level (not workflow level) to check
+  `github.event.workflow_run.conclusion == 'success'`. Job-level conditions are evaluated at
+  runtime after the event fires, so this reliably gates deployment on CI success.
+
+  Do NOT put the `if:` check at the workflow level — it prevents ALL jobs from running,
+  including any cleanup or notification jobs that should run regardless of conclusion.
+
+  For workflows that need to handle both success and failure (e.g., notify Slack of failures),
+  use separate jobs with different `if:` checks.
+fix_code:
+  - language: yaml
+    label: 'Add conclusion check at the job level — most common fix'
+    code: |
+      name: Deploy
+
+      on:
+        workflow_run:
+          workflows: [CI]
+          types: [completed]
+
+      jobs:
+        deploy:
+          # ✅ Only deploy when CI succeeded
+          if: github.event.workflow_run.conclusion == 'success'
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+              with:
+                # workflow_run always checks out default branch — use ref for PR branches
+                ref: ${{ github.event.workflow_run.head_sha }}
+            - run: ./deploy.sh
+  - language: yaml
+    label: 'Branch by conclusion — deploy on success, notify on failure'
+    code: |
+      name: Post-CI Actions
+
+      on:
+        workflow_run:
+          workflows: [CI]
+          types: [completed]
+
+      jobs:
+        deploy:
+          if: github.event.workflow_run.conclusion == 'success'
+          runs-on: ubuntu-latest
+          steps:
+            - run: ./deploy.sh
+
+        notify-failure:
+          if: >-
+            github.event.workflow_run.conclusion == 'failure' ||
+            github.event.workflow_run.conclusion == 'timed_out'
+          runs-on: ubuntu-latest
+          steps:
+            - name: Notify team of CI failure
+              run: |
+                echo "CI failed on branch ${{ github.event.workflow_run.head_branch }}"
+                # Send Slack/Teams notification here
+  - language: yaml
+    label: 'Anti-pattern: missing conclusion check silently deploys broken code'
+    code: |
+      # ❌ BAD: Runs even when CI failed, was cancelled, or was skipped by path filter
+      on:
+        workflow_run:
+          workflows: [CI]
+          types: [completed]   # "completed" means ANY outcome, not just success
+
+      jobs:
+        deploy:
+          # No if: conclusion check — deploys broken code on CI failure!
+          runs-on: ubuntu-latest
+          steps:
+            - run: ./deploy.sh
+prevention:
+  - "Always add `if: github.event.workflow_run.conclusion == 'success'` to deploy/release jobs triggered by workflow_run"
+  - "Remember: 'completed' means the upstream workflow finished — NOT that it succeeded; always check conclusion explicitly"
+  - "Use separate jobs with different `if: conclusion ==` checks for success vs failure vs cancelled handling"
+  - "Consider adding a linting step or actionlint check that flags workflow_run jobs without a conclusion check"
+  - "Test the failure path by intentionally failing CI and verifying the downstream workflow does NOT deploy"
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#workflow_run'
+    label: 'GitHub Docs: workflow_run event — conclusion field and types'
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#github-context'
+    label: 'GitHub Docs: github.event.workflow_run context properties'
+  - url: 'https://stackoverflow.com/questions/62750603/github-actions-trigger-another-action-after-one-action-is-completed'
+    label: 'SO #62750603: Trigger action after completion — top answer adds conclusion check (159 upvotes, 152k views)'
+  - url: 'https://github.com/ahmadnassri/action-workflow-run-wait'
+    label: 'ahmadnassri/action-workflow-run-wait — third-party action created to wait for successful workflow_run'

package/errors/triggers/triggers-074.yml

@@ -0,0 +1,142 @@
+id: triggers-074
+title: '`workflow_run: branches:` filter silently never triggers when upstream was started by `schedule` or `workflow_dispatch` — `head_branch` is null'
+category: triggers
+severity: silent-failure
+tags:
+  - workflow-run
+  - branches-filter
+  - head-branch
+  - schedule
+  - workflow-dispatch
+  - null
+  - silent-failure
+  - trigger-missing
+patterns:
+  - regex: 'on:\s*\n\s+workflow_run:\s*\n(.|\n)*?branches:\s*\n'
+    flags: 'im'
+  - regex: 'workflow_run.*branches.*schedule\s*$|schedule.*workflow_run.*branches'
+    flags: 'im'
+error_messages:
+  - "# No error message — the downstream workflow simply never runs when upstream was triggered by schedule or workflow_dispatch"
+root_cause: |
+  The `workflow_run` event exposes a `branches:` filter that is supposed to limit which upstream
+  workflow run conclusions trigger the downstream workflow. The filter compares against
+  `github.event.workflow_run.head_branch`.
+
+  **The problem:** When the upstream workflow is triggered by a `schedule` or `workflow_dispatch`
+  event, GitHub sets `head_branch` to `null` (not a branch name). The `branches:` filter then
+  evaluates `null` against each pattern in the list — and null never matches any branch name
+  pattern, including `[main]`, `['**']`, or any glob. The downstream workflow silently never
+  triggers, even though the upstream ran successfully on main.
+
+  **Event types that produce null head_branch:**
+  - `schedule` — cron-triggered workflows have no associated branch context
+  - `workflow_dispatch` — manually dispatched workflows MAY have null head_branch in some cases
+
+  **Pull request triggers correctly populate head_branch** (the PR head branch name), and
+  `push` triggers also correctly populate it (the pushed branch name). The null behavior is
+  specific to schedule and dispatch events on the upstream.
+
+  **Why this is a silent failure:**
+  - No error is raised — the downstream workflow simply does not appear in the Actions UI for that run
+  - The upstream workflow runs and completes successfully
+  - The `branches:` filter looks correct — `[main]` is the right branch name
+  - The issue only manifests for schedule/dispatch-triggered upstream runs; if CI also triggers
+    on push to main, push-triggered runs DO reach the downstream workflow
+
+  **Example scenario:** A deploy workflow runs after CI. CI has `on: [push, schedule]`.
+  The `branches: [main]` filter in the deploy's workflow_run block works for push events but
+  silently skips all scheduled CI runs.
+
+  Sources: GitHub Docs (workflow_run, head_branch null for schedule); community/discussions
+  related to workflow_run not triggering after schedule; documented in
+  `workflow-run-head-branch-null-schedule-dispatch-concurrency.yml` (concurrency variant)
+fix: |
+  Remove the `branches:` filter from the `workflow_run` trigger entirely and instead use a
+  job-level `if:` condition to check the branch after the event fires. The `if:` condition
+  evaluates at runtime and can handle null gracefully.
+
+  For schedule-triggered upstreams, use `github.event.workflow_run.head_branch == 'main' ||
+  github.event.workflow_run.head_branch == null` (null means it ran from the default branch).
+
+  Alternatively, filter by the workflow run's `head_sha` and check against known branch SHAs.
+fix_code:
+  - language: yaml
+    label: 'Remove branches filter and add job-level if condition — handles schedule and dispatch'
+    code: |
+      name: Deploy After CI
+
+      on:
+        workflow_run:
+          workflows: [CI]
+          types: [completed]
+          # ❌ Do NOT use branches: here if CI runs on schedule or workflow_dispatch
+          # branches: [main]   # This silently skips all schedule-triggered CI runs
+
+      jobs:
+        deploy:
+          # ✅ Use job-level if: instead of trigger-level branches:
+          # null head_branch means schedule/dispatch from default branch — include it
+          if: >-
+            github.event.workflow_run.conclusion == 'success' &&
+            (github.event.workflow_run.head_branch == 'main' ||
+             github.event.workflow_run.head_branch == null)
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - run: ./deploy.sh
+  - language: yaml
+    label: 'When upstream is push-only: branches filter works fine (head_branch is always set)'
+    code: |
+      name: Deploy After CI (push-only upstream)
+
+      on:
+        workflow_run:
+          workflows: [CI]
+          types: [completed]
+          # ✅ branches: filter works correctly ONLY when upstream runs on push or pull_request
+          # Because push and pull_request events always set head_branch
+          branches: [main]
+
+      jobs:
+        deploy:
+          if: github.event.workflow_run.conclusion == 'success'
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - run: ./deploy.sh
+
+      # ⚠️ If CI also has on: schedule — add null check above or remove branches: filter
+  - language: yaml
+    label: 'Anti-pattern: branches filter with schedule-triggered upstream — downstream never fires'
+    code: |
+      # ❌ BAD: Upstream CI has on: [push, schedule]
+      # But deploy's branches filter silently skips all scheduled CI runs
+
+      name: Deploy After CI
+
+      on:
+        workflow_run:
+          workflows: [CI]
+          types: [completed]
+          branches: [main]   # null (from schedule) never matches 'main' — deploy skipped!
+
+      jobs:
+        deploy:
+          if: github.event.workflow_run.conclusion == 'success'
+          runs-on: ubuntu-latest
+          steps:
+            - run: ./deploy.sh   # Never runs after scheduled CI
+prevention:
+  - "Avoid `branches:` filter in workflow_run if the upstream workflow can be triggered by `schedule` or `workflow_dispatch`"
+  - "Use job-level `if:` conditions with explicit null handling instead of trigger-level branch filters"
+  - "Check the upstream workflow's triggers — if it includes `schedule` or `workflow_dispatch`, `head_branch` will be null for those runs"
+  - "Test by triggering the upstream workflow manually and verifying the downstream workflow appears in the Actions UI"
+  - "When null head_branch is acceptable (schedule from default branch), use `head_branch == 'main' || head_branch == null`"
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#workflow_run'
+    label: 'GitHub Docs: workflow_run event — branches filter and head_branch field'
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#github-context'
+    label: 'GitHub Docs: github.event.workflow_run — head_branch property (null for schedule/dispatch)'
+  - url: 'https://github.com/orgs/community/discussions/26238'
+    label: 'GitHub Community: workflow_run not triggering — head_branch null discussion'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@htekdev/actions-debugger",
-  "version": "1.0.131",
+  "version": "1.0.132",
   "description": "65+ real GitHub Actions errors, queryable by agents. CLI + MCP server + Copilot skills + error database.",
   "type": "module",
   "main": "./dist/index.js",