@htekdev/actions-debugger 1.0.74 → 1.0.76

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/permissions-auth/org-policy-blocks-pr-creation-despite-pull-requests-write.yml

@@ -0,0 +1,115 @@
+id: permissions-auth-047
+title: "Org-Level Policy Blocks GitHub Actions from Creating or Approving Pull Requests Even with pull-requests: write"
+category: permissions-auth
+severity: error
+tags:
+  - pull-requests
+  - permissions
+  - org-policy
+  - github-token
+  - create-pr
+  - branch-protection
+patterns:
+  - regex: 'GitHub Actions is not permitted to create or approve pull requests'
+    flags: 'i'
+  - regex: 'Resource not accessible by integration'
+    flags: 'i'
+  - regex: 'HttpError.*403.*pull request'
+    flags: 'i'
+error_messages:
+  - "GitHub Actions is not permitted to create or approve pull requests."
+  - "HttpError: Resource not accessible by integration"
+  - "Error: 403 - {\"message\":\"GitHub Actions is not permitted to create or approve pull requests.\",\"documentation_url\":\"https://docs.github.com/rest/pulls/pulls\"}"
+  - "Error: Validation Failed: pull request creation is not allowed for this repository"
+root_cause: |
+  GitHub enforces a two-level policy hierarchy for GitHub Actions creating or
+  approving pull requests:
+
+  1. **Organization level** — GitHub organization owners must enable
+     "Allow GitHub Actions to create and approve pull requests" under:
+     Organization Settings → Actions → General → Workflow permissions
+
+  2. **Repository level** — After the org-level setting is enabled, each repository
+     can independently enable or disable the same option. The repo-level option is
+     grayed out and non-interactive until the org-level gate is open.
+
+  3. **Enterprise level** — For GitHub Enterprise accounts, the same setting must
+     also be enabled at the enterprise level (Enterprise Settings → Actions → General)
+     before it can be configured at the org level.
+
+  Adding `permissions: pull-requests: write` (or `permissions: write-all`) to the
+  workflow YAML only controls the GITHUB_TOKEN's OAuth scope. The org/enterprise policy
+  is an additional administrative gate enforced by the GitHub API regardless of what
+  the token is scoped for. The token can have `pull-requests: write` scope but still
+  receive HTTP 403 if the org policy is disabled.
+
+  The repo-level "Read and write permissions" setting in repo Settings → Actions → General
+  is a second distinct control — it sets the token's default permissions but still
+  cannot override a disabled org-level policy.
+fix: |
+  Step 1 — Enable the setting at the **organization level** (requires org owner):
+    https://github.com/organizations/YOUR_ORG/settings/actions
+    Under "Workflow permissions" → check "Allow GitHub Actions to create and approve pull requests"
+
+  Step 2 — Enable the setting at the **repository level** (the option is now clickable):
+    https://github.com/YOUR_ORG/YOUR_REPO/settings/actions
+    Under "Workflow permissions" → check "Allow GitHub Actions to create and approve pull requests"
+
+  Step 3 — Add the permission to the workflow file:
+    permissions: pull-requests: write (plus contents: write if creating commits)
+
+  For GitHub Enterprise: also enable at enterprise level first:
+    https://github.com/enterprises/YOUR_ENTERPRISE/settings/actions
+
+  For personal accounts (no org):
+    Go to Repository Settings → Actions → General → Workflow permissions →
+    set "Read and write permissions".
+fix_code:
+  - language: yaml
+    label: "Add required permissions to the workflow job"
+    code: |
+      jobs:
+        create-pr:
+          runs-on: ubuntu-latest
+          permissions:
+            contents: write       # required to push branches
+            pull-requests: write  # required to create/comment on PRs
+          steps:
+            - uses: actions/checkout@v4
+            - name: Create Pull Request
+              uses: peter-evans/create-pull-request@v6
+              with:
+                title: 'chore: automated update'
+                branch: 'automated/update'
+  - language: yaml
+    label: "Using gh CLI to create a PR (also requires pull-requests: write + org policy enabled)"
+    code: |
+      jobs:
+        open-pr:
+          runs-on: ubuntu-latest
+          permissions:
+            contents: write
+            pull-requests: write
+          steps:
+            - uses: actions/checkout@v4
+            - name: Open PR
+              env:
+                GH_TOKEN: ${{ github.token }}
+              run: |
+                gh pr create \
+                  --title "chore: automated update" \
+                  --body "Created by GitHub Actions" \
+                  --base main \
+                  --head "${{ github.ref_name }}"
+prevention:
+  - "Before building PR-automation workflows, verify the org-level 'Allow GitHub Actions to create and approve pull requests' setting is enabled."
+  - "Check the setting at all applicable levels — enterprise (if applicable) → organization → repository."
+  - "Always declare explicit `permissions:` in workflows that create PRs; do not rely on repository defaults."
+  - "Use `permissions: pull-requests: write` at the job level (not workflow level) to minimize token scope."
+docs:
+  - url: "https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests"
+    label: "GitHub Docs — Preventing GitHub Actions from creating or approving pull requests"
+  - url: "https://docs.github.com/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-creating-or-approving-pull-requests"
+    label: "GitHub Docs — Org-level: disabling GitHub Actions from creating pull requests"
+  - url: "https://stackoverflow.com/questions/72376229/github-actions-is-not-permitted-to-create-or-approve-pull-requests"
+    label: "SO: GitHub Actions is not permitted to create or approve pull requests (67 votes, 40k views)"

package/errors/runner-environment/bash-set-e-grep-no-matches-exit-1.yml

@@ -0,0 +1,103 @@
+id: runner-environment-137
+title: "bash -eo pipefail Default Causes grep Exit Code 1 (No Matches) to Fail the Step"
+category: runner-environment
+severity: error
+tags:
+  - bash
+  - grep
+  - pipefail
+  - set-e
+  - shell
+  - exit-code
+patterns:
+  - regex: 'Error: Process completed with exit code 1\.'
+    flags: 'i'
+  - regex: 'grep.*exit code 1'
+    flags: 'i'
+root_cause: |
+  GitHub Actions `run:` steps on Linux/macOS use `bash -e {0}` by default when no
+  `shell:` is specified. When `shell: bash` is explicitly set, the shell is invoked
+  as `bash --noprofile --norc -eo pipefail {0}`, adding `-o pipefail`.
+
+  The key behavior:
+  - `-e` (set -e) — any command that exits non-zero immediately aborts the whole step.
+  - `grep` returns exit code 1 when it finds zero matches (not an error in the shell
+    sense, but a non-zero exit). Combined with `-e`, a `grep` that matches nothing
+    kills the step with "Error: Process completed with exit code 1."
+  - The issue is silent — the step log shows the grep command output (or no output)
+    and then suddenly fails. Developers who test locally (where `set -e` is not the
+    default interactive shell setting) never reproduce the failure.
+
+  Common triggers:
+  - `grep -c pattern file` when pattern not found → exits 1
+  - `git log | grep "pattern"` in CI where the pattern is absent
+  - Variable assignment: `COUNT=$(echo "$LIST" | grep -c "value")` — if grep exits 1,
+    the subshell exits 1, and `-e` aborts the parent step
+error_messages:
+  - "Error: Process completed with exit code 1."
+  - "##[error]Process completed with exit code 1."
+fix: |
+  Several options depending on your use case:
+
+  Option 1 — Disable fail-fast for a specific command using `|| true`:
+  Append `|| true` to any grep command where zero matches is acceptable. The `|| true`
+  ensures the overall expression always exits 0.
+
+  Option 2 — Disable `set -e` for the entire step with `shell: bash {0}`:
+  Using `{0}` as the script placeholder removes the `-e` flag. Use this when you need
+  full control over exit codes throughout the step.
+
+  Option 3 — Use `set +e` at the top of the run block to disable fail-fast for all
+  subsequent commands, then selectively handle errors manually.
+
+  Option 4 — Use grep's `--quiet` / `-q` flag and evaluate with an `if` statement,
+  never relying on exit code propagation.
+fix_code:
+  - language: yaml
+    label: "WRONG — grep exit code 1 kills step when no match found"
+    code: |
+      - name: Count matches
+        run: |
+          COUNT=$(echo "$DIFF" | grep -c "src/my_folder")
+          echo "Changed files: $COUNT"
+  - language: yaml
+    label: "CORRECT — append || true to grep commands where zero matches is valid"
+    code: |
+      - name: Count matches
+        run: |
+          COUNT=$(echo "$DIFF" | grep -c "src/my_folder" || true)
+          echo "Changed files: $COUNT"
+  - language: yaml
+    label: "CORRECT — disable set -e for entire step with shell: bash {0}"
+    code: |
+      - name: Count matches
+        shell: bash {0}
+        run: |
+          COUNT=$(echo "$DIFF" | grep -c "src/my_folder")
+          echo "Changed files: $COUNT"
+          # now exit codes must be checked manually
+  - language: yaml
+    label: "CORRECT — use grep -q with explicit if for boolean presence check"
+    code: |
+      - name: Check for changes
+        run: |
+          if echo "$DIFF" | grep -q "src/my_folder"; then
+            echo "Changes detected in src/my_folder"
+          else
+            echo "No changes in src/my_folder"
+          fi
+prevention:
+  - "Append `|| true` to any `grep`, `awk`, or other command where a non-zero exit is not an error."
+  - "Use `shell: bash {0}` (no `-e`) for steps that need fine-grained exit code handling."
+  - "Prefer `grep -q` with `if/else` blocks instead of relying on grep exit codes for flow control."
+  - "Test CI scripts locally with `bash -e script.sh` to reproduce the fail-fast behavior."
+  - "Use `set -o pipefail` explicitly when you need pipeline failures to surface, and document it."
+docs:
+  - url: "https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell"
+    label: "jobs.<job_id>.steps[*].shell — default shell invocation"
+  - url: "https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference"
+    label: "Exit codes and error action preference"
+  - url: "https://stackoverflow.com/questions/73066461/github-actions-why-an-intermediate-command-failure-in-shell-script-would-cause"
+    label: "SO: Why an intermediate command failure causes the whole step to fail (17 votes)"
+  - url: "https://stackoverflow.com/questions/75419587/does-a-github-action-step-use-set-e-semantics-by-default"
+    label: "SO: Does a GitHub action step use set -e semantics by default? (13 votes)"

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/runner-environment/npm-ci-cross-platform-optional-native-binary-missing.yml

@@ -0,0 +1,113 @@
+id: runner-environment-138
+title: "npm ci Cross-Platform Lockfile Missing Optional Native Binaries (esbuild, rollup, vite)"
+category: runner-environment
+severity: error
+tags:
+  - npm
+  - npm-ci
+  - esbuild
+  - rollup
+  - vite
+  - optional-dependencies
+  - cross-platform
+  - lockfile
+  - native-binary
+patterns:
+  - regex: 'Cannot find module @rollup/rollup-linux-x64'
+    flags: 'i'
+  - regex: 'You installed esbuild (on|for) another platform'
+    flags: 'i'
+  - regex: 'Cannot find module @esbuild/linux'
+    flags: 'i'
+  - regex: 'npm has a bug related to optional dependencies'
+    flags: 'i'
+error_messages:
+  - "Cannot find module @rollup/rollup-linux-x64-gnu"
+  - "Cannot find module @rollup/rollup-linux-x64-musl"
+  - "You installed esbuild on another platform than the one you're currently using"
+  - "Cannot find module @esbuild/linux-x64"
+  - "npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory."
+root_cause: |
+  Modern JavaScript bundlers (rollup, vite, esbuild, SWC, Turbopack) ship platform-
+  specific optional native binaries as separate npm packages — e.g.,
+  `@rollup/rollup-linux-x64-gnu`, `@esbuild/darwin-arm64`, `@esbuild/linux-x64`.
+
+  When a developer runs `npm install` on macOS (darwin-arm64 or darwin-x64), the
+  generated `package-lock.json` records the macOS-specific optional packages but NOT
+  the Linux equivalents. GitHub-hosted runners run on Linux. When `npm ci` uses
+  this macOS-generated lockfile in CI:
+
+  1. `npm ci` correctly installs exactly what's in the lockfile — only the macOS
+     native binary entries are present.
+  2. The Linux-specific optional dependency (`@rollup/rollup-linux-x64-gnu`) is
+     absent from the lockfile, so `npm ci` never installs it.
+  3. The build step then fails because the required native binary is missing.
+
+  This was a long-standing npm bug (npm/cli#4828) that was fixed in npm 11.3.0
+  (shipped with Node.js 24.0.2). On older npm versions the issue must be worked around.
+
+  Note: `npm ci` itself succeeds — the failure occurs downstream during the build/test
+  step that imports the native module.
+fix: |
+  Option 1 (recommended for npm 11.3.0+ / Node.js 24.0.2+):
+  Update Node.js to 24.0.2 or npm to 11.3.0+, then regenerate the lockfile with
+  `npm install` from scratch. The bug is fixed in this version.
+
+  Option 2 — Explicitly list the Linux optional dependencies in `package.json`:
+  Add all required platform-native packages to the `optionalDependencies` section.
+  npm will then include them in the lockfile regardless of the OS where it was generated.
+
+  Option 3 — Regenerate the lockfile in CI using `npm install --package-lock-only`
+  before running `npm ci`. This is slow but guarantees the lockfile matches the runner OS.
+
+  Option 4 — Use a Linux environment locally (Docker, WSL2, or devcontainer) to
+  generate the lockfile so it contains Linux-specific entries.
+fix_code:
+  - language: yaml
+    label: "Option 2 — Add Linux optional native packages to package.json optionalDependencies"
+    code: |
+      # In package.json, add the Linux optional dependency explicitly:
+      # "optionalDependencies": {
+      #   "@rollup/rollup-linux-x64-gnu": "*"
+      # }
+      # Then run npm install locally to regenerate the lockfile.
+      # In your workflow, npm ci will now install it on Linux runners.
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - uses: actions/setup-node@v4
+              with:
+                node-version: '20'
+                cache: 'npm'
+            - run: npm ci
+            - run: npm run build
+  - language: yaml
+    label: "Option 1 — Use Node.js 24+ where the bug is fixed"
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - uses: actions/setup-node@v4
+              with:
+                node-version: '24'   # npm 11.3.0+ ships with Node 24.0.2+
+                cache: 'npm'
+            - run: npm ci
+            - run: npm run build
+prevention:
+  - "Pin your team's lockfile generation to Linux (use devcontainers, Docker, or WSL2 on Windows)."
+  - "Upgrade to Node.js 24.0.2+ or npm 11.3.0+ where the optional dependency platform bug is fixed."
+  - "If cross-platform lockfiles are unavoidable, explicitly add platform-specific packages to `optionalDependencies` in `package.json`."
+  - "After adding `optionalDependencies`, regenerate the lockfile from scratch — delete `package-lock.json` and `node_modules`, then run `npm install`."
+docs:
+  - url: "https://stackoverflow.com/questions/79048814/github-action-is-failing-due-to-rollup-rollup-linux-x64-gnu"
+    label: "SO: Github Action failing due to @rollup/rollup-linux-x64-gnu (13 votes, 8k views)"
+  - url: "https://stackoverflow.com/questions/73139649/you-installed-esbuild-on-another-platform-than-the-one-youre-currently-using"
+    label: "SO: You installed esbuild on another platform (36 votes, 51k views)"
+  - url: "https://github.com/npm/cli/issues/4828"
+    label: "npm/cli#4828 — Optional dependencies not installed for different platform"
+  - url: "https://vitejs.dev/guide/troubleshooting#vite-cjs-node-api-deprecated"
+    label: "Vite troubleshooting — esbuild platform mismatch"

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/triggers/required-status-check-not-in-branch-protection-dropdown.yml

@@ -0,0 +1,115 @@
+id: triggers-052
+title: "Required Status Check Not Appearing in Branch Protection Dropdown"
+category: triggers
+severity: limitation
+tags:
+  - branch-protection
+  - required-status-check
+  - check-name
+  - job-name
+  - workflow-name
+  - protected-branch
+patterns:
+  - regex: 'status check.*not found'
+    flags: 'i'
+  - regex: 'waiting for status to be reported'
+    flags: 'i'
+error_messages:
+  - "Waiting for status to be reported"
+  - "Required status check is expected — check name not found in the dropdown"
+root_cause: |
+  Branch protection required status checks have several constraints that cause them
+  to silently not appear in the "Status checks that are required" search dropdown:
+
+  1. **Wrong name searched** — The check name in branch protection is the job's
+     `name:` field (if set) or the job's YAML key (ID) — NOT the workflow's `name:`
+     field. Developers often search for the workflow name and can't find the check.
+     For matrix jobs, the check name includes matrix values:
+     e.g., `build (ubuntu-latest, 20.x)` not just `build`.
+
+  2. **Check must have run recently** — A status check only appears in the dropdown
+     after it has completed successfully at least once on that repository within the
+     past 7 days. Brand-new workflows that have never been triggered won't show up.
+
+  3. **Workflow must target the protected branch** — For PR-triggered checks, the
+     workflow must have `on: pull_request: branches: [main]` (or the target branch).
+     A workflow that only runs on `push` to feature branches never posts a status
+     to main's pull requests.
+
+  4. **Paths filters suppressing the check** — If the workflow has `paths:` filters,
+     PRs that don't change filtered files never trigger the workflow, so the check
+     is absent (causing PRs to be permanently stuck as "Waiting"). This is covered
+     separately in `required-status-check-paths-filter-pr-stuck.yml`.
+
+  All of these issues are silent — no error is shown. The dropdown simply doesn't
+  include the expected check name.
+fix: |
+  Step 1 — Confirm the exact check name:
+  Go to any recently-merged or open PR in the repository. Find the check in the
+  PR's "Checks" tab. Copy the exact displayed name — it is the job's `name:` field
+  or the YAML job key, not the workflow `name:` at the top of the file.
+  For matrix jobs, include the matrix combination: `build (ubuntu-latest, 20.x)`.
+
+  Step 2 — Trigger the workflow at least once on a PR against the protected branch:
+  The check must have a successful run within the past 7 days to appear.
+  Create a test PR or push a temporary commit to get the first run.
+
+  Step 3 — Add a descriptive `name:` to each job that will be a required check.
+  This makes the check name human-readable and stable even if you rename the job key.
+
+  Step 4 — For matrix workflows, consider adding a fanout job (a job that `needs:`
+  all matrix jobs) with a simple pass/fail step, and set THAT as the required check.
+  This avoids needing to list every matrix combination individually in branch protection.
+fix_code:
+  - language: yaml
+    label: "Add explicit job name for a stable, searchable required status check name"
+    code: |
+      jobs:
+        build:
+          name: "CI Build"   # This is the check name in branch protection, NOT 'build'
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - run: npm ci && npm test
+  - language: yaml
+    label: "Matrix jobs — add a fanout job to use as the single required check"
+    code: |
+      jobs:
+        test:
+          name: "Test (${{ matrix.os }}, Node ${{ matrix.node }})"
+          runs-on: ${{ matrix.os }}
+          strategy:
+            matrix:
+              os: [ubuntu-latest, windows-latest]
+              node: ['18', '20']
+          steps:
+            - uses: actions/checkout@v4
+            - uses: actions/setup-node@v4
+              with:
+                node-version: ${{ matrix.node }}
+            - run: npm ci && npm test
+
+        all-tests-pass:
+          name: "All Tests Pass"   # Set THIS as the required status check
+          needs: test
+          runs-on: ubuntu-latest
+          if: always()
+          steps:
+            - name: Verify all matrix jobs passed
+              run: |
+                if [[ "${{ needs.test.result }}" != "success" ]]; then
+                  echo "One or more test matrix jobs failed"
+                  exit 1
+                fi
+prevention:
+  - "Always add a `name:` to jobs that will be required status checks — job IDs change when refactoring."
+  - "Trigger the workflow at least once before setting up branch protection, so the check appears in the dropdown."
+  - "For matrix jobs, add a dedicated fanout job that passes only when all matrix jobs pass; set it as the required check."
+  - "Avoid `paths:` filters on required-check workflows — use them on optional checks only, or use `required-status-check-paths-filter-pr-stuck.yml` workaround."
+docs:
+  - url: "https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/troubleshooting-required-status-checks"
+    label: "GitHub Docs — Troubleshooting required status checks"
+  - url: "https://stackoverflow.com/questions/68554735/github-action-status-check-missing-from-the-list-of-checks-in-protected-branch-s"
+    label: "SO: Github Action Status check missing from Protected branch settings (75 votes, 29k views)"
+  - url: "https://stackoverflow.com/questions/61989951/github-action-workflow-not-running"
+    label: "SO: GitHub Action workflow not running (158 votes, 202k views)"

package/package.json

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