@htekdev/actions-debugger 1.0.73 → 1.0.75

package/errors/caching-artifacts/cache-post-step-skipped-on-job-failure.yml

@@ -0,0 +1,127 @@
+id: caching-artifacts-044
+title: 'actions/cache post step skipped when job fails — cache not saved on failure (post-if: success() default)'
+category: caching-artifacts
+severity: silent-failure
+tags:
+  - actions-cache
+  - cache-save
+  - job-failure
+  - post-if
+  - save-always
+  - silent-skip
+patterns:
+  - regex: 'Post\s+Run\s+actions/cache'
+    flags: 'i'
+  - regex: 'save-always'
+    flags: 'i'
+  - regex: 'Cache\s+not\s+found'
+    flags: 'i'
+error_messages:
+  - "Cache was not saved. Exiting with failure."
+  - "Post Run actions/cache@v4 skipped"
+  - "Cache miss on subsequent run after failed job"
+  - "cache-hit: false even though previous run had cache action"
+root_cause: |
+  actions/cache (v3 and v4) uses a `post-if: success()` condition on the cache save post step
+  by default. This means the cache save step only runs when ALL preceding steps in the job
+  succeeded. When any step fails:
+  - The job transitions to "failure" state
+  - The cache post step is SKIPPED silently — no warning, annotation, or error is logged
+  - The next run gets a cache miss and must re-download/rebuild from scratch
+
+  This is commonly discovered when:
+  - A test suite installs dependencies (cached) then runs tests (which fail)
+  - The cache works on the first run but never again after a flaky failure
+  - A build step fails, wasting all compilation work that could have been cached
+  - CI is slow because each failed run discards the cache and rebuilds from zero
+
+  Note: This is DIFFERENT from caching-artifacts-036 which covers the case where the job
+  is CANCELLED (via concurrency cancel-in-progress). Cancellation also skips the post step,
+  but for a different reason — cancellation interrupts all runners immediately.
+
+  The failure case is separate: the job runs to completion (with a failure), the post step
+  lifecycle still runs, but the post-if condition evaluates to false and skips it silently.
+fix: |
+  Option 1 (recommended): Set `save-always: true` on the restore step (actions/cache v3.3.3+ and v4+):
+    - uses: actions/cache@v4
+      with:
+        path: ~/.npm
+        key: ${{ runner.os }}-node-${{ hashFiles('package-lock.json') }}
+        save-always: true   # Save cache even if job fails
+
+  Option 2: Use the standalone cache/save action in an explicit cleanup step:
+    - uses: actions/cache/restore@v4
+      id: cache-restore
+      with:
+        path: ~/.npm
+        key: ${{ runner.os }}-node-${{ hashFiles('package-lock.json') }}
+    - run: npm ci
+    - uses: actions/cache/save@v4
+      if: always()   # Explicit save even on failure
+      with:
+        path: ~/.npm
+        key: ${{ runner.os }}-node-${{ hashFiles('package-lock.json') }}
+
+  Option 3 (v3 only): Use `cache-v3-save-always-unexpected-input` — note that `save-always`
+  was not available before v3.3.3. On older versions, use the split restore/save approach.
+fix_code:
+  - language: yaml
+    label: 'Save cache on job failure using save-always: true (v4)'
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+
+            - uses: actions/cache@v4
+              with:
+                path: ~/.npm
+                key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
+                restore-keys: |
+                  ${{ runner.os }}-npm-
+                save-always: true   # Cache saves even if subsequent steps fail
+
+            - run: npm ci
+            - run: npm test         # If this fails, cache is still saved
+  - language: yaml
+    label: 'Explicit restore then save with if: always() (works on all versions)'
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+
+            - name: Restore cache
+              id: npm-cache
+              uses: actions/cache/restore@v4
+              with:
+                path: ~/.npm
+                key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
+                restore-keys: |
+                  ${{ runner.os }}-npm-
+
+            - run: npm ci
+            - run: npm test
+
+            - name: Save cache (always, even on failure)
+              uses: actions/cache/save@v4
+              if: always()
+              with:
+                path: ~/.npm
+                key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
+prevention:
+  - 'Add save-always: true to actions/cache when partial installs (e.g., npm ci with an error) are still worth caching'
+  - 'Consider whether caching a partial/failed state is desirable — for compiled artifacts, only cache on success'
+  - 'Use the split restore/save action pattern for fine-grained control over when the cache is saved'
+  - 'Monitor cache hit rates in the Actions UI — consistently low rates after failures indicate post-if skips'
+docs:
+  - url: 'https://github.com/actions/cache#save-cache-even-if-the-build-fails'
+    label: 'actions/cache — save-always: true option'
+  - url: 'https://github.com/actions/cache/blob/main/save/README.md'
+    label: 'actions/cache/save — standalone save action'
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows'
+    label: 'GitHub Docs — Caching dependencies to speed up workflows'
+  - url: 'https://github.com/actions/cache/issues/92'
+    label: 'actions/cache#92 — Feature request: save cache on failure (highly voted)'

package/errors/concurrency-timing/push-pr-ref-format-different-concurrency-no-sharing.yml

@@ -0,0 +1,113 @@
+id: concurrency-timing-038
+title: 'push and pull_request events use different github.ref formats — concurrency slots never shared between event types'
+category: concurrency-timing
+severity: silent-failure
+tags:
+  - concurrency
+  - github-ref
+  - pull-request
+  - push
+  - cancel-in-progress
+  - slot-sharing
+patterns:
+  - regex: 'group:\s+\$\{\{\s*github\.workflow\s*\}\}-\$\{\{\s*github\.ref\s*\}\}'
+    flags: 'i'
+  - regex: 'refs/pull/\d+/merge'
+    flags: ''
+error_messages:
+  - "Push deploy and PR deploy run in parallel despite same concurrency group"
+  - "concurrency group does not prevent push and pull_request from running simultaneously"
+  - "Both workflows triggered at the same time even with concurrency group set"
+root_cause: |
+  When concurrency group uses `${{ github.ref }}`, the ref value differs by event type:
+  - `on: push` to main → github.ref = 'refs/heads/main'
+  - `on: pull_request` targeting main → github.ref = 'refs/pull/123/merge' (synthetic merge ref)
+
+  These produce different concurrency group keys, so push and pull_request runs NEVER share
+  a concurrency slot. Developers who want "one deploy at a time" across push and PR events
+  are surprised when both run in parallel.
+
+  Common scenario:
+  - Deploy workflow triggers on both push (to main) and pull_request (for preview)
+  - A push to main is deploying
+  - A new PR triggers a deploy
+  - Both run simultaneously because their github.ref values are different strings
+  - Race condition or resource contention on the deployment target
+
+  This is distinct from the `github.head_ref` empty-on-push issue (which over-cancels).
+  Here, using `github.ref` under-cancels by never sharing slots between event types.
+fix: |
+  To serialize push and pull_request deploys into one slot, use a ref-agnostic key
+  or normalize the ref to a shared value.
+
+  Option 1: Use a static concurrency key scoped to just the workflow name (one slot total):
+    group: ${{ github.workflow }}
+    cancel-in-progress: true
+
+  Option 2: Normalize to the target/base branch using head_ref for PRs and ref_name for push:
+    group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
+    cancel-in-progress: true
+
+  For github.head_ref || github.ref_name:
+  - pull_request: github.head_ref = 'feature/my-branch' (PR source branch)
+  - push:        github.ref_name = 'main' (pushed branch name)
+  - Both give meaningful branch names, but they still differ — PRs use source branch, push uses target
+  - For "one deploy to main at a time" across both events, use github.base_ref || github.ref_name
+
+  Option 3: Use the target/base branch for both:
+    group: ${{ github.workflow }}-${{ github.base_ref || github.ref_name }}
+    cancel-in-progress: true
+  - pull_request: github.base_ref = 'main' (target branch)
+  - push:        github.ref_name = 'main' (pushed branch)
+  - Both produce the same key for operations targeting main — serializes push and PR deploys
+fix_code:
+  - language: yaml
+    label: 'Serialize push and pull_request deploys to the same target branch'
+    code: |
+      on:
+        push:
+          branches: [main]
+        pull_request:
+          branches: [main]
+
+      concurrency:
+        # Use base_ref (PR target) or ref_name (push branch) — both equal 'main'
+        # when targeting main, so push and PR deploys share one slot
+        group: ${{ github.workflow }}-${{ github.base_ref || github.ref_name }}
+        cancel-in-progress: true
+
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          steps:
+            - name: Deploy
+              run: echo "Deploying to ${{ github.base_ref || github.ref_name }}"
+  - language: yaml
+    label: 'One global slot for the entire workflow (simplest serialization)'
+    code: |
+      on:
+        push:
+          branches: [main]
+        pull_request:
+
+      concurrency:
+        group: ${{ github.workflow }}
+        cancel-in-progress: true
+
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          steps:
+            - run: echo "Only one run at a time, any trigger"
+prevention:
+  - 'Understand that github.ref differs between push (refs/heads/BRANCH) and pull_request (refs/pull/N/merge) events'
+  - 'Use github.base_ref || github.ref_name to get the target/base branch name for both event types'
+  - 'Test concurrency behavior with simultaneous push and PR triggers before relying on it for deploy serialization'
+  - 'Use github.head_ref for the PR source branch or github.ref_name for push branch — never github.ref directly in concurrency keys unless same-event-type serialization is the goal'
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/controlling-concurrency'
+    label: 'GitHub Actions — Controlling concurrency'
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#github-context'
+    label: 'GitHub context — github.ref, github.head_ref, github.base_ref, github.ref_name'
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#pull_request'
+    label: 'pull_request event — github.ref is refs/pull/N/merge'

package/errors/known-unsolved/github-step-summary-not-accessible-cross-job.yml

@@ -0,0 +1,132 @@
+id: known-unsolved-046
+title: 'GITHUB_STEP_SUMMARY content is not accessible by downstream jobs or reusable workflows'
+category: known-unsolved
+severity: limitation
+tags:
+  - github-step-summary
+  - step-summary
+  - cross-job
+  - job-outputs
+  - reusable-workflow
+  - limitation
+patterns:
+  - regex: 'GITHUB_STEP_SUMMARY'
+    flags: 'i'
+  - regex: 'step.summary'
+    flags: 'i'
+error_messages:
+  - "Cannot read GITHUB_STEP_SUMMARY from another job"
+  - "Step summary not available as job output"
+  - "How to share step summary content between jobs"
+root_cause: |
+  `GITHUB_STEP_SUMMARY` is a write-only file path for adding Markdown content to the job
+  summary page in the GitHub Actions UI. The content written to it is visible in the UI
+  but is NOT accessible programmatically from:
+  - Other jobs in the same workflow (even with `needs:` dependency)
+  - Downstream caller workflows that invoke this as a reusable workflow
+  - Workflow run APIs — the summary content cannot be retrieved via the REST API
+
+  The summary file exists only on the runner's local filesystem during execution and is
+  uploaded to GitHub as display-only content. There is no `steps.<id>.summary` output
+  or `needs.<job>.summary` context available.
+
+  Common failure patterns:
+  - Build job writes a changelog summary; deploy job tries to use it in a notification
+  - Reusable workflow summarizes test results; caller tries to aggregate summaries
+  - Reporting job expects to read markdown generated by upstream jobs
+
+  GitHub has no native mechanism to read back summary content once written.
+  This is a long-standing requested feature with no announced roadmap.
+fix: |
+  Use job outputs or artifacts to share data that needs to be readable by downstream jobs.
+  GITHUB_STEP_SUMMARY is display-only — treat it as a write-once UI annotation.
+
+  Workaround 1 — Dual-write (write to both summary AND output/artifact):
+    Write the same content to GITHUB_STEP_SUMMARY for display AND to $GITHUB_OUTPUT or
+    an artifact for programmatic consumption by downstream jobs.
+
+  Workaround 2 — Generate in a script and capture output:
+    Run the data-generation logic in a script, capture to a variable, write to both
+    $GITHUB_STEP_SUMMARY and $GITHUB_OUTPUT in the same step.
+
+  There is no workaround that reads GITHUB_STEP_SUMMARY after it has been written.
+  Data sharing between jobs MUST use job outputs or artifacts.
+fix_code:
+  - language: yaml
+    label: 'Dual-write: populate GITHUB_STEP_SUMMARY for UI AND job output for downstream use'
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          outputs:
+            changelog: ${{ steps.gen.outputs.changelog }}
+          steps:
+            - name: Generate changelog
+              id: gen
+              run: |
+                CHANGES=$(git log --oneline HEAD~5..HEAD)
+
+                # Write to step summary for UI display
+                echo "## Changes" >> $GITHUB_STEP_SUMMARY
+                echo "$CHANGES" >> $GITHUB_STEP_SUMMARY
+
+                # Also write to output for downstream job consumption
+                # Use heredoc for multiline output
+                {
+                  echo "changelog<<EOF"
+                  echo "$CHANGES"
+                  echo "EOF"
+                } >> $GITHUB_OUTPUT
+
+        notify:
+          needs: build
+          runs-on: ubuntu-latest
+          steps:
+            - name: Use changelog from build job
+              run: |
+                echo "Changes to notify: ${{ needs.build.outputs.changelog }}"
+  - language: yaml
+    label: 'Upload summary content as artifact for reusable workflow callers'
+    code: |
+      jobs:
+        test:
+          runs-on: ubuntu-latest
+          steps:
+            - name: Run tests and generate report
+              run: |
+                # Write display summary
+                echo "## Test Results" >> $GITHUB_STEP_SUMMARY
+                echo "All tests passed" >> $GITHUB_STEP_SUMMARY
+
+                # Write machine-readable copy to a file (upload as artifact)
+                echo "All tests passed" > test-summary.md
+
+            - name: Upload summary as artifact
+              uses: actions/upload-artifact@v4
+              with:
+                name: test-summary
+                path: test-summary.md
+
+        deploy:
+          needs: test
+          runs-on: ubuntu-latest
+          steps:
+            - name: Download test summary
+              uses: actions/download-artifact@v4
+              with:
+                name: test-summary
+
+            - name: Use test summary
+              run: cat test-summary.md
+prevention:
+  - 'Never assume GITHUB_STEP_SUMMARY content can be read back — it is write-only display output'
+  - 'Design workflows to use job outputs ($GITHUB_OUTPUT) or artifacts for any data that must flow between jobs'
+  - 'Write data to both GITHUB_STEP_SUMMARY (for UI) and $GITHUB_OUTPUT (for downstream) in the same step when both are needed'
+  - 'Document this limitation for team members who discover it while trying to aggregate summaries across jobs'
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#adding-a-job-summary'
+    label: 'GitHub Docs — Adding a job summary (GITHUB_STEP_SUMMARY)'
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/passing-information-between-jobs'
+    label: 'GitHub Docs — Passing information between jobs (outputs and artifacts)'
+  - url: 'https://github.com/orgs/community/discussions/12836'
+    label: 'GitHub Community — Read GITHUB_STEP_SUMMARY from downstream jobs (no native support)'

package/errors/known-unsolved/reusable-workflow-local-action-path-resolves-to-called-repo.yml

@@ -0,0 +1,114 @@
+id: known-unsolved-047
+title: "Reusable workflow uses: ./local-action resolves relative to the called repo, not the calling repo"
+category: known-unsolved
+severity: limitation
+tags:
+  - reusable-workflow
+  - composite-action
+  - path-resolution
+  - local-action
+  - cross-repo
+  - limitation
+patterns:
+  - regex: 'Can''t find ''action\.ya?ml'''
+    flags: 'i'
+  - regex: 'Unable to resolve action.*\.\/'
+    flags: 'i'
+  - regex: 'action\.ya?ml.*does not exist'
+    flags: 'i'
+error_messages:
+  - "Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/repo/repo/local-action'"
+  - "Unable to resolve action `./local-action`, unable to find 'action.yaml' or 'action.yml'"
+  - "Error: Can't find 'action.yml' for step uses: ./shared-actions/deploy"
+root_cause: |
+  When a reusable workflow file (stored in org/shared-workflows) contains steps that
+  reference local composite actions using relative paths (uses: ./path/to/action), the
+  path resolves relative to the CALLED (reusable) repository — not the CALLING
+  repository.
+
+  Resolution rule: In any workflow file, uses: ./path always resolves to the root of
+  the repository that CONTAINS the workflow YAML file.
+
+  So in org/shared-workflows/.github/workflows/ci.yml:
+    - uses: ./actions/lint  →  looks in org/shared-workflows/actions/lint/action.yml
+    - Does NOT look in org/app-repo/actions/lint/ (the calling repo)
+
+  This means teams cannot:
+  - Share a reusable workflow that calls composite actions defined in the CALLING repo
+  - Have callers "inject" local actions into a shared reusable workflow via relative paths
+  - Centralize reusable workflows in one repo while composite actions stay in team repos
+
+  This limitation is by design and has been acknowledged by the GitHub Actions team as
+  a fundamental architectural constraint. The calling repository's workspace may be
+  checked out during the job, but action path resolution happens at workflow evaluation
+  time using the workflow file's own repository root, not the runtime workspace.
+fix: |
+  There is no direct fix — this is a platform-level path resolution limitation.
+
+  Option 1 (recommended) — Co-locate composite actions in the same repository as the
+  reusable workflow and reference them with uses: ./path (resolves correctly).
+
+  Option 2 — Publish shared composite actions to a dedicated standalone repository
+  (e.g., org/shared-actions) and reference them with the full path:
+    uses: org/shared-actions/path/to-action@main
+
+  Option 3 — Pass all data that the local action would have computed as inputs to the
+  reusable workflow, removing the need for the caller's local action inside the callee.
+fix_code:
+  - language: yaml
+    label: "Co-locate composite action in the same repo as the reusable workflow"
+    code: |
+      # Repository: org/shared-workflows
+      # Structure:
+      #   .github/
+      #     workflows/
+      #       ci.yml              <- reusable workflow
+      #     actions/
+      #       shared-lint/
+      #         action.yml        <- composite action lives HERE (same repo)
+
+      # In org/shared-workflows/.github/workflows/ci.yml:
+      on:
+        workflow_call:
+          inputs:
+            source-directory:
+              type: string
+              required: true
+
+      jobs:
+        lint:
+          runs-on: ubuntu-latest
+          steps:
+            # Resolves to org/shared-workflows/.github/actions/shared-lint
+            - uses: ./.github/actions/shared-lint
+              with:
+                src-path: ${{ inputs.source-directory }}
+
+  - language: yaml
+    label: "Reference composite action from a standalone shared repo"
+    code: |
+      # Instead of: uses: ./local-action (broken — resolves to reusable workflow's repo)
+      # Use the full repo reference pointing to org/shared-actions:
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: org/shared-actions/deploy@v2
+              with:
+                environment: ${{ inputs.environment }}
+            - uses: org/shared-actions/notify@v2
+              with:
+                status: ${{ job.status }}
+
+prevention:
+  - "Keep reusable workflow files and their local composite action dependencies in the same repository"
+  - "Publish composite actions shared across many repositories to a dedicated org/shared-actions repo"
+  - "Test reusable workflows by calling them from a different repository early in development"
+  - "Document which composite actions a reusable workflow depends on and where they must be located"
+docs:
+  - url: "https://docs.github.com/en/actions/sharing-automations/reusing-workflows"
+    label: "GitHub docs — Reusing workflows"
+  - url: "https://docs.github.com/en/actions/sharing-automations/creating-actions/about-custom-actions#choosing-a-location-for-your-action"
+    label: "GitHub docs — Choosing a location for your action"
+  - url: "https://github.com/orgs/community/discussions/17244"
+    label: "GitHub Community discussion — local composite action reference from reusable workflow"

package/errors/runner-environment/github-script-require-module-not-found.yml

@@ -0,0 +1,98 @@
+id: runner-environment-136
+title: "actions/github-script require() of third-party npm packages fails with MODULE_NOT_FOUND"
+category: runner-environment
+severity: error
+tags:
+  - github-script
+  - nodejs
+  - require
+  - npm
+  - module-not-found
+  - third-party-package
+patterns:
+  - regex: 'Cannot find module'
+    flags: 'i'
+  - regex: 'MODULE_NOT_FOUND'
+    flags: ''
+error_messages:
+  - "Error: Cannot find module 'axios'"
+  - "Error: Cannot find module 'lodash'"
+  - "Error: Cannot find module 'js-yaml'"
+  - "Error: Cannot find module 'semver'"
+  - "Cannot find module at /home/runner/work/_actions/actions/github-script/v7/lib/async-function.js:1"
+root_cause: |
+  The actions/github-script action executes scripts in a sandboxed Node.js runtime that
+  only includes packages bundled with the action itself. Built-in parameters available
+  in the script context are:
+    - github  — authenticated Octokit client (@octokit/rest)
+    - context — workflow event context
+    - core    — @actions/core
+    - glob    — @actions/glob
+    - io      — @actions/io
+    - exec    — @actions/exec
+    - fetch   — Node.js built-in fetch (Node 18+)
+
+  Any call to require() for packages NOT in this list — such as axios, lodash, js-yaml,
+  semver, chalk, or any other npm package — will fail with MODULE_NOT_FOUND because the
+  packages are not installed in the runner environment that executes the script.
+
+  The action does NOT auto-install packages from the repo's package.json or any other
+  manifest. Node.js module resolution only searches paths within the bundled action's
+  own node_modules directory, which contains only the above built-ins.
+fix: |
+  Option 1 (install before use) — Run npm install in a prior step and reference the
+  package via full path using RUNNER_TEMP or GITHUB_WORKSPACE:
+    - name: Install npm package
+      run: npm install <package-name>
+      working-directory: ${{ runner.temp }}
+    - uses: actions/github-script@v7
+      with:
+        script: |
+          const pkg = require(process.env.RUNNER_TEMP + '/node_modules/<package-name>')
+
+  Option 2 (use built-ins) — Refactor to use only the built-in parameters. For HTTP
+  requests use fetch() instead of axios; for YAML parsing use a run: step with a script
+  file.
+
+  Option 3 (separate Node.js script) — Move complex logic into a .js file in the repo
+  and run it with node in a run: step after npm install, giving full package access.
+fix_code:
+  - language: yaml
+    label: "Install package before github-script and require via RUNNER_TEMP"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+
+        - name: Install axios for github-script
+          run: npm install axios
+          working-directory: ${{ runner.temp }}
+
+        - uses: actions/github-script@v7
+          with:
+            script: |
+              const axios = require(process.env.RUNNER_TEMP + '/node_modules/axios')
+              const { data } = await axios.get('https://api.example.com/status')
+              core.setOutput('api-status', data.status)
+
+  - language: yaml
+    label: "Replace axios with built-in fetch() (Node 18+, no require needed)"
+    code: |
+      steps:
+        - uses: actions/github-script@v7
+          with:
+            script: |
+              // fetch is built-in — no require() needed (Node 18+, github-script v7+)
+              const response = await fetch('https://api.example.com/status')
+              const data = await response.json()
+              core.setOutput('api-status', data.status)
+
+prevention:
+  - "Check the github-script README 'Built-in variables' section before adding require() calls"
+  - "Use fetch() (built-in from Node 18+ / github-script v7+) instead of axios for HTTP requests"
+  - "For complex logic needing many npm packages, use a separate script file with a run: node step"
+  - "Consider caching the npm install step if packages are large or installed frequently"
+docs:
+  - url: "https://github.com/actions/github-script?tab=readme-ov-file#built-in-variables"
+    label: "actions/github-script — Built-in variables (official README)"
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/using-github-script-in-a-workflow"
+    label: "GitHub docs — Using GitHub Script in a workflow"

package/errors/silent-failures/env-block-sibling-key-reference-empty-string.yml

@@ -0,0 +1,92 @@
+id: silent-failures-071
+title: "${{ env.VAR }} in a step's env: block evaluates to empty string when VAR is a sibling key in the same block"
+category: silent-failures
+severity: silent-failure
+tags:
+  - env-context
+  - expression
+  - env-block
+  - sibling-reference
+  - empty-string
+  - configuration
+patterns:
+  - regex: 'env\.\w+\}\}.*\{\{\s*env\.\w+'
+    flags: 'i'
+error_messages:
+  - "(no error message — step runs successfully but env var is assigned an incorrect partial value)"
+root_cause: |
+  When multiple environment variables are defined in the same step (or job) env: block
+  and one attempts to compose a value from a sibling key using ${{ env.X }}, the
+  reference silently evaluates to an EMPTY STRING.
+
+  GitHub Actions evaluates all expressions in an env: block BEFORE the step runs, using
+  the env context that exists at that point in time. That context includes:
+    - Variables defined in the workflow-level env: block
+    - Variables defined in the job-level env: block (jobs.<id>.env)
+    - Variables added by previous steps via $GITHUB_ENV
+
+  It does NOT include sibling keys defined elsewhere in the SAME env: block being
+  evaluated. The block is evaluated atomically — each value is expanded using only
+  the env context from BEFORE the block, not from within it.
+
+  Example of the mistake:
+    env:
+      BASE_URL: https://api.example.com    # this is fine
+      FULL_URL: ${{ env.BASE_URL }}/v2     # SILENTLY wrong: evaluates to "/v2"
+
+  FULL_URL becomes "/v2" (not "https://api.example.com/v2") because BASE_URL is not
+  in the env context at the time the step's env: block expressions are evaluated —
+  it is only available AFTER the step starts executing.
+
+  This is a silent failure: no warning is produced, the step succeeds, and the
+  misconfigured variable is silently assigned the wrong value.
+fix: |
+  Option 1 (recommended) — Move the "base" variable to the workflow-level or job-level
+  env: block so it is already in the env context when the step's env: block is evaluated.
+
+  Option 2 — Compose the derived value inside the run: step using shell variable
+  expansion, which operates at runtime when all variables are already set.
+
+  Option 3 — Use an expression based on inputs, vars, or secrets contexts which ARE
+  fully available during env: block evaluation.
+fix_code:
+  - language: yaml
+    label: "Hoist base variable to workflow-level env so it's in context"
+    code: |
+      # Define BASE_URL at workflow level — it will be in the env context
+      env:
+        BASE_URL: https://api.example.com
+
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          steps:
+            - name: Call API
+              run: curl "$FULL_URL"
+              env:
+                # env.BASE_URL is available here because it's defined at workflow level
+                FULL_URL: ${{ env.BASE_URL }}/v2/endpoint
+
+  - language: yaml
+    label: "Compose the value inside run: using shell variable expansion"
+    code: |
+      steps:
+        - name: Call API endpoint
+          run: |
+            # Shell variable composition works at runtime when BASE_URL is already set
+            FULL_URL="${BASE_URL}/v2/endpoint"
+            curl "$FULL_URL"
+          env:
+            BASE_URL: https://api.example.com
+            # FULL_URL built in shell — no need to compose in env: block
+
+prevention:
+  - "Define 'base' env vars at workflow or job level when they need to be referenced by step-level env: blocks"
+  - "Use shell variable composition inside run: steps rather than ${{ env.X }} in the same env: block"
+  - "Verify composed env var values by printing them with echo before use in critical steps"
+  - "Review GitHub Actions context availability documentation when authoring env: blocks"
+docs:
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/variables#using-the-env-context-to-access-environment-variable-values"
+    label: "GitHub docs — Using the env context to access environment variable values"
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/contexts#context-availability"
+    label: "GitHub docs — Context availability table"

package/errors/triggers/create-event-fires-for-branch-and-tag.yml

@@ -0,0 +1,108 @@
+id: triggers-051
+title: "on: create event fires for both branch and tag creation — must filter with github.ref_type"
+category: triggers
+severity: silent-failure
+tags:
+  - create-event
+  - delete-event
+  - ref-type
+  - tag
+  - branch
+  - trigger-filter
+  - release
+patterns:
+  - regex: 'on:\s*[\r\n]+\s+create:'
+    flags: 'i'
+error_messages:
+  - "(no error message — workflow triggers unexpectedly on branch creation, not just tag creation)"
+root_cause: |
+  The on: create event triggers whenever ANY ref (branch OR tag) is created in the
+  repository. There is no built-in filter to restrict it to only tag creation or only
+  branch creation.
+
+  Many developers use on: create expecting to run release or version-publish workflows
+  only when a version tag is pushed, but the workflow also fires for:
+    - Feature branches created via the GitHub UI or API
+    - Dependabot version update branches (dependabot/npm_and_yarn/...)
+    - Automated branches created by bots or scripts
+    - PR branches created by tooling
+    - Any branch creation event from any actor
+
+  The github.ref_type context variable ('branch' or 'tag') is available in the run
+  context but on: create has no built-in filter for it — an explicit if: condition
+  on the job or step must be used to restrict execution.
+
+  The same behavior applies to on: delete — it fires for both branch and tag deletion.
+fix: |
+  Add an if: condition at the job level (or step level) to filter by github.ref_type:
+
+    jobs:
+      release:
+        if: github.ref_type == 'tag'   # restrict to tag creation only
+
+  Alternative: Use on: push with a tags: filter instead of on: create.
+  The push event with tags: filter is more explicit, supports glob patterns,
+  and does not fire for branch operations at all.
+fix_code:
+  - language: yaml
+    label: "Filter on: create to tags only using ref_type job condition"
+    code: |
+      on:
+        create:
+
+      jobs:
+        release:
+          runs-on: ubuntu-latest
+          # Only run for tag creation (e.g., v1.2.3), not branch creation
+          if: github.ref_type == 'tag'
+          steps:
+            - uses: actions/checkout@v4
+            - name: Build and publish release
+              run: echo "Publishing ${{ github.ref_name }}"
+
+  - language: yaml
+    label: "Preferred: use on: push with tags filter for tag-triggered workflows"
+    code: |
+      # More explicit and common pattern for release workflows
+      on:
+        push:
+          tags:
+            - 'v*.*.*'        # triggers on v1.0.0, v2.3.1, etc.
+            # - 'v[0-9]+.*'   # alternative glob
+
+      jobs:
+        release:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - name: Build and publish release
+              run: echo "Publishing ${{ github.ref_name }}"
+
+  - language: yaml
+    label: "Filter on: delete to branch deletion only (e.g., branch cleanup)"
+    code: |
+      on:
+        delete:
+
+      jobs:
+        cleanup:
+          runs-on: ubuntu-latest
+          # Only run for branch deletion, not tag deletion
+          if: github.ref_type == 'branch'
+          steps:
+            - name: Cleanup branch resources
+              run: echo "Cleaning up resources for ${{ github.ref_name }}"
+
+prevention:
+  - "Always add if: github.ref_type == 'tag' when using on: create for release/publish workflows"
+  - "Prefer on: push with tags: filter for tag-triggered release workflows — it's more explicit"
+  - "Add if: github.ref_type == 'branch' when using on: delete for branch cleanup automation"
+  - "Test create/delete workflows by creating a feature branch to verify it does NOT trigger unexpectedly"
+  - "Review all on: create workflows in the repository after adding Dependabot — it creates many branches"
+docs:
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#create"
+    label: "GitHub docs — create event"
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#delete"
+    label: "GitHub docs — delete event"
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/contexts#github-context"
+    label: "GitHub docs — github context (ref_type field)"

package/errors/yaml-syntax/workflow-call-inputs-no-choice-type.yml

@@ -0,0 +1,121 @@
+id: yaml-syntax-048
+title: 'workflow_call inputs do not support type: choice — validation error when copying from workflow_dispatch'
+category: yaml-syntax
+severity: error
+tags:
+  - workflow-call
+  - reusable-workflow
+  - inputs
+  - type-choice
+  - workflow-dispatch
+  - validation-error
+patterns:
+  - regex: 'Unexpected\s+value\s+[''"]choice[''"]'
+    flags: 'i'
+  - regex: 'type:\s+choice'
+    flags: 'i'
+  - regex: 'on\.workflow_call\.inputs\.[^.]+\.type.*choice'
+    flags: 'i'
+error_messages:
+  - "Unexpected value 'choice'"
+  - "Invalid workflow file: .github/workflows/deploy.yml#L12: Unexpected value 'choice'"
+  - "on.workflow_call.inputs.environment.type: Unexpected value 'choice'"
+  - "inputs.environment.options: Unexpected value"
+root_cause: |
+  GitHub Actions supports two input type systems that are NOT identical:
+  - workflow_dispatch inputs support: string, choice, boolean, environment, number
+  - workflow_call inputs support:     string, boolean, number ONLY
+
+  The `choice` type (with its `options:` list) is exclusive to workflow_dispatch manual triggers.
+  Reusable workflows (workflow_call) do not support `type: choice` or the `options:` field.
+
+  This error is most commonly hit when:
+  1. A developer builds a manual workflow_dispatch workflow with choice inputs
+  2. They convert it to a reusable workflow by changing `on: workflow_dispatch` to `on: workflow_call`
+  3. They leave the `type: choice` and `options:` keys intact
+  4. The workflow fails validation with "Unexpected value 'choice'"
+
+  Example invalid workflow_call input:
+    on:
+      workflow_call:
+        inputs:
+          environment:
+            type: choice        # ERROR: not supported in workflow_call
+            options:            # ERROR: not supported in workflow_call
+              - staging
+              - production
+            required: true
+fix: |
+  Change `type: choice` to `type: string` in workflow_call inputs and remove the `options:` key.
+  To enforce valid values, validate the input inside the workflow body using an `if:` condition
+  or a run step that exits on invalid input.
+
+  The calling workflow or documentation should enumerate the valid values since workflow_call
+  cannot enforce them at the input schema level.
+fix_code:
+  - language: yaml
+    label: 'workflow_call input with string type and manual validation (called workflow)'
+    code: |
+      # .github/workflows/deploy-reusable.yml
+      on:
+        workflow_call:
+          inputs:
+            environment:
+              type: string        # Change 'choice' to 'string'
+              required: true
+              description: 'Target environment: staging or production'
+              # No 'options:' key — not supported in workflow_call
+
+      jobs:
+        validate-input:
+          runs-on: ubuntu-latest
+          steps:
+            - name: Validate environment input
+              run: |
+                if [[ "${{ inputs.environment }}" != "staging" && "${{ inputs.environment }}" != "production" ]]; then
+                  echo "Invalid environment: ${{ inputs.environment }}"
+                  echo "Valid values: staging, production"
+                  exit 1
+                fi
+
+        deploy:
+          needs: validate-input
+          runs-on: ubuntu-latest
+          environment: ${{ inputs.environment }}
+          steps:
+            - run: echo "Deploying to ${{ inputs.environment }}"
+  - language: yaml
+    label: 'Calling workflow passing the environment string input'
+    code: |
+      # .github/workflows/deploy-caller.yml
+      on:
+        workflow_dispatch:
+          inputs:
+            environment:
+              type: choice        # choice IS supported here in workflow_dispatch
+              options:
+                - staging
+                - production
+              required: true
+
+      jobs:
+        call-deploy:
+          uses: ./.github/workflows/deploy-reusable.yml
+          with:
+            environment: ${{ inputs.environment }}  # Pass validated string to reusable
+          secrets: inherit
+prevention:
+  - 'workflow_call inputs only support type: string, boolean, and number — never type: choice or type: environment'
+  - 'Keep workflow_dispatch wrappers that expose choice inputs and call the reusable workflow internally'
+  - 'Document the valid values for string inputs in the description field of workflow_call inputs'
+  - 'Add an explicit validation step at the start of the reusable workflow to enforce allowed values'
+  - 'Use actionlint to catch unsupported input types before pushing the workflow file'
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#workflow_call'
+    label: 'GitHub Docs — workflow_call inputs (string, boolean, number only)'
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#workflow_dispatch'
+    label: 'GitHub Docs — workflow_dispatch inputs (includes choice, environment types)'
+  - url: 'https://docs.github.com/en/actions/sharing-automations/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow'
+    label: 'GitHub Docs — Reusable workflow inputs and secrets'
+  - url: 'https://github.com/orgs/community/discussions/39357'
+    label: 'GitHub Community — workflow_call does not support type: choice inputs'

package/package.json

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