@htekdev/actions-debugger 1.0.19 → 1.0.20

package/errors/permissions-auth/fine-grained-pat-org-restricted-forbidden.yml

@@ -0,0 +1,104 @@
+id: permissions-auth-024
+title: "Fine-Grained PATs Blocked by Organization Policy — 'forbidden from accessing this repository'"
+category: permissions-auth
+severity: error
+tags:
+  - fine-grained-pat
+  - organization-policy
+  - personal-access-token
+  - authentication
+  - 403
+patterns:
+  - regex: "Fine-grained personal access tokens are forbidden from accessing this repository"
+    flags: "i"
+  - regex: "fine.grained.*forbidden|forbidden.*fine.grained"
+    flags: "i"
+  - regex: "personal access tokens.*not permitted|PAT.*restricted"
+    flags: "i"
+error_messages:
+  - "remote: Fine-grained personal access tokens are forbidden from accessing this repository."
+  - "fatal: unable to access 'https://github.com/org/repo.git/': The requested URL returned error: 403"
+  - "Fine-grained personal access tokens are forbidden from accessing this repository."
+root_cause: |
+  GitHub organizations can restrict which types of PATs are allowed to access their
+  resources. When an organization enables "Restrict access via fine-grained personal
+  access tokens" (or sets PAT policy to "Disable fine-grained personal access tokens"),
+  any fine-grained PAT — regardless of its scopes or permissions — will be rejected
+  with a 403 error containing the message "Fine-grained personal access tokens are
+  forbidden from accessing this repository."
+
+  This policy applies even if:
+  - The fine-grained PAT has all required permissions (contents: write, etc.)
+  - The PAT was created by an org owner
+  - The repository is public
+  - The user is an org admin
+
+  Common confusion: developers who switch from classic PATs to fine-grained PATs
+  for better security/granularity hit this org-level block and cannot understand
+  why a seemingly correct token still fails with 403.
+
+  Sources: stackoverflow.com/questions/79471500,
+           GitHub Docs on PAT policies for organizations
+fix: |
+  Option 1 (Immediate fix): Use a classic PAT with the required scopes instead of
+  a fine-grained PAT. Classic PATs are not subject to the fine-grained restriction.
+
+  Option 2 (Organization change — requires admin): Have an org admin update the
+  organization's PAT policy to allow fine-grained PATs:
+    Settings → Developer Settings → Personal access token policy
+    → Allow fine-grained personal access tokens
+    → (optionally require approval for each token)
+
+  Option 3 (Recommended long-term): Replace the PAT with a GitHub App token.
+  GitHub App tokens are not subject to org-level PAT restrictions and provide
+  better auditability and short-lived credentials.
+fix_code:
+  - language: yaml
+    label: "Use classic PAT (immediate workaround)"
+    code: |
+      # Replace the fine-grained PAT secret with a classic PAT:
+      # GitHub.com > Settings > Developer settings > Personal access tokens > Tokens (classic)
+      # Create new token with required scopes (e.g., repo)
+      # Add to repo secrets as CLASSIC_PAT
+
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+              with:
+                token: ${{ secrets.CLASSIC_PAT }}
+                # Classic PATs work even when org blocks fine-grained PATs
+  - language: yaml
+    label: "Use a GitHub App token (recommended)"
+    code: |
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          steps:
+            - name: Generate GitHub App token
+              id: app-token
+              uses: actions/create-github-app-token@v1
+              with:
+                app-id: ${{ vars.APP_ID }}
+                private-key: ${{ secrets.APP_PRIVATE_KEY }}
+                owner: ${{ github.repository_owner }}
+              # GitHub App tokens bypass org-level PAT restrictions entirely
+
+            - uses: actions/checkout@v4
+              with:
+                token: ${{ steps.app-token.outputs.token }}
+prevention:
+  - "Before using fine-grained PATs for org repositories, verify the org allows them via Settings → Third-party access → Personal access tokens."
+  - "Document the org's PAT policy in your CI/onboarding docs so contributors know which token types are accepted."
+  - "Prefer GitHub App tokens over any PAT type — they are not subject to PAT restriction policies and provide short-lived, auditable credentials."
+  - "When a PAT fails with 403, check if the error message contains 'fine-grained' before debugging scopes — the token type itself may be blocked."
+docs:
+  - url: "https://docs.github.com/en/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization"
+    label: "Setting a PAT policy for your organization"
+  - url: "https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens"
+    label: "Managing personal access tokens"
+  - url: "https://stackoverflow.com/questions/79471500/github-actions-authentication-failed-for-pushing-to-repository"
+    label: "SO: GitHub Actions — Authentication Failed for Pushing to Repository (fine-grained PAT forbidden)"
+  - url: "https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/making-authenticated-api-requests-with-a-github-app-in-a-github-actions-workflow"
+    label: "Using GitHub App tokens in GitHub Actions"

package/errors/permissions-auth/pat-sso-org-not-authorized-checkout-404.yml

@@ -0,0 +1,107 @@
+id: permissions-auth-023
+title: "PAT Fails with 'Not Found' on SSO-Protected Organization Repository"
+category: permissions-auth
+severity: error
+tags:
+  - personal-access-token
+  - saml-sso
+  - organization
+  - checkout
+  - authentication
+patterns:
+  - regex: "Not Found - https://docs\\.github\\.com/rest/repos/repos#get-a-repository"
+    flags: "i"
+  - regex: "fatal: unable to access.*403|Syncing repository.*Not Found"
+    flags: "i"
+  - regex: "could not read Username.*https://github\\.com"
+    flags: "i"
+error_messages:
+  - "Not Found - https://docs.github.com/rest/repos/repos#get-a-repository"
+  - "Retrieving the default branch name"
+  - "  Not Found - https://docs.github.com/rest/repos/repos#get-a-repository"
+  - "Error: Not Found - https://docs.github.com/rest/repos/repos#get-a-repository"
+root_cause: |
+  When a GitHub organization enforces SAML SSO (Single Sign-On), every PAT
+  (Personal Access Token) used to access that organization's resources must be
+  explicitly authorized for the SSO organization — even if the token has all the
+  correct scopes (repo, read:org, etc.).
+
+  A PAT that hasn't been authorized for the SSO org will receive a 404 "Not Found"
+  response when attempting to access org resources via the API or when cloning/
+  checking out a repository. The response is 404 (not 401/403) because GitHub
+  treats an unauthorized SSO request as "resource doesn't exist for this token."
+
+  Common symptoms:
+  - `actions/checkout` fails with "Not Found" on the default branch retrieval step
+  - The PAT works locally in a browser (which has an active SSO session) but fails
+    in GitHub Actions
+  - The token has `repo` scope or `contents: read` permission but still 404s
+
+  Sources: stackoverflow.com/questions/79874764,
+           stackoverflow.com/questions/77957649,
+           GitHub Docs on SAML SSO authorization
+fix: |
+  Authorize the PAT for the SSO organization:
+
+  1. Go to GitHub → Settings → Developer settings → Personal access tokens
+  2. Select the PAT used in the workflow
+  3. Click "Configure SSO" next to the token
+  4. Click "Authorize" next to the target organization
+  5. Complete any SSO prompts
+
+  The PAT is now authorized for that org and will work in Actions workflows.
+
+  For fine-grained PATs: ensure the token's "Resource owner" is the organization
+  (not your personal account) and that the org admin has approved it.
+fix_code:
+  - language: yaml
+    label: "Authorize the PAT for SSO org (no workflow change needed)"
+    code: |
+      # This is a GitHub settings action, not a workflow change.
+      # GitHub.com > Settings > Developer settings > Personal access tokens
+      # > (select token) > Configure SSO > Authorize > (org name)
+      #
+      # After authorizing, your workflow using the PAT will work:
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+              with:
+                repository: my-org/private-repo
+                token: ${{ secrets.MY_ORG_PAT }}
+                # MY_ORG_PAT must have 'repo' scope AND be SSO-authorized for my-org
+  - language: yaml
+    label: "Use a GitHub App token instead (recommended for SSO orgs)"
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          steps:
+            - name: Generate GitHub App token
+              id: app-token
+              uses: actions/create-github-app-token@v1
+              with:
+                app-id: ${{ vars.APP_ID }}
+                private-key: ${{ secrets.APP_PRIVATE_KEY }}
+                owner: my-org
+                # GitHub App tokens for org installations are not subject to
+                # SAML SSO PAT authorization requirements
+            - uses: actions/checkout@v4
+              with:
+                repository: my-org/private-repo
+                token: ${{ steps.app-token.outputs.token }}
+prevention:
+  - "After creating a new PAT for use with an SSO-enforcing organization, always authorize it via Configure SSO before adding it to Actions secrets."
+  - "Test PAT access locally with `gh auth login --with-token` and `gh repo view my-org/repo` to confirm SSO authorization before using in CI."
+  - "Prefer GitHub App tokens over PATs for organization repositories — they are not subject to SAML SSO authorization requirements."
+  - "Document which secrets require SSO authorization in your repo's CONTRIBUTING or CI documentation to prevent the same issue for new contributors."
+docs:
+  - url: "https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on"
+    label: "Authorizing a PAT for use with SAML SSO"
+  - url: "https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on"
+    label: "About SAML SSO for organizations"
+  - url: "https://stackoverflow.com/questions/79874764/github-actions-checkout-fails-with-not-found-error-for-sso-protected-enterprise"
+    label: "SO: checkout fails with Not Found for SSO-protected enterprise repo"
+  - url: "https://stackoverflow.com/questions/77957649/repository-not-found-error-while-using-actions-checkoutv4-to-clone-a-private-re"
+    label: "SO: Repository not found error with actions/checkout@v4 on private repo"

package/errors/runner-environment/docker-buildx-matrix-platform-tag-overwrite.yml

@@ -0,0 +1,143 @@
+id: runner-environment-052
+title: "Docker Multi-Platform Build Uses Matrix per Platform — Tags Overwrite Each Other"
+category: runner-environment
+severity: silent-failure
+tags:
+  - docker
+  - buildx
+  - multi-platform
+  - matrix
+  - ghcr
+  - manifest
+patterns:
+  - regex: "no matching manifest for .* in the manifest list entries"
+    flags: "i"
+  - regex: "image operating system .* does not match host operating system"
+    flags: "i"
+  - regex: "manifest unknown"
+    flags: "i"
+error_messages:
+  - "no matching manifest for linux/amd64 in the manifest list entries"
+  - "Error response from daemon: manifest unknown: manifest unknown"
+  - "image operating system \"linux\" does not match host operating system \"linux\""
+root_cause: |
+  A common pattern for multi-platform Docker images in GitHub Actions is to use
+  `strategy.matrix` with one platform per job and `docker/build-push-action` in
+  each job. This approach is incorrect: each job pushes a single-platform image
+  to the same tag, and each push *overwrites* the previous one. There is no merging
+  of single-platform images into a multi-platform manifest list.
+
+  After all matrix jobs complete, the tag only contains the image from the last
+  job to push — typically whichever platform finished last. All other platforms are
+  silently lost.
+
+  When another host tries to pull the image on a different architecture (e.g.,
+  linux/arm64 pulling after linux/amd64 was last to write), they receive:
+  "no matching manifest for linux/arm64 in the manifest list entries"
+
+  The workflow itself reports success — all matrix jobs push successfully. The
+  failure is silent until image consumers on other architectures try to pull.
+
+  Sources: stackoverflow.com/questions/79315376,
+           Docker multi-platform build documentation
+fix: |
+  Use a single `docker/build-push-action` step with comma-separated platforms
+  instead of a matrix. Docker Buildx handles building all platforms in one job
+  and pushes a proper multi-platform manifest list.
+
+  If you need dedicated builders for each platform (e.g., native ARM runners),
+  use the "bake + merge manifest" pattern with `docker buildx imagetools create`
+  to merge per-platform digests into a single manifest after all builds complete.
+fix_code:
+  - language: yaml
+    label: "Single buildx job with comma-separated platforms (recommended)"
+    code: |
+      jobs:
+        build-and-push:
+          runs-on: ubuntu-latest
+          permissions:
+            packages: write
+            contents: read
+          steps:
+            - uses: actions/checkout@v4
+
+            - name: Set up QEMU
+              uses: docker/setup-qemu-action@v3
+
+            - name: Set up Docker Buildx
+              uses: docker/setup-buildx-action@v3
+
+            - name: Login to GHCR
+              uses: docker/login-action@v3
+              with:
+                registry: ghcr.io
+                username: ${{ github.actor }}
+                password: ${{ secrets.GITHUB_TOKEN }}
+
+            - name: Build and push multi-platform image
+              uses: docker/build-push-action@v6
+              with:
+                push: true
+                platforms: linux/amd64,linux/arm64,linux/arm/v7
+                # All platforms in one step → proper manifest list created
+                tags: ghcr.io/${{ github.repository_owner }}/myapp:latest
+  - language: yaml
+    label: "Native-builder pattern: build per platform, merge manifest (advanced)"
+    code: |
+      # Build per-platform in parallel jobs, then merge into a manifest list
+      jobs:
+        build:
+          strategy:
+            matrix:
+              include:
+                - platform: linux/amd64
+                  runner: ubuntu-latest
+                - platform: linux/arm64
+                  runner: ubuntu-24.04-arm  # native ARM runner
+          runs-on: ${{ matrix.runner }}
+          outputs:
+            digest: ${{ steps.push.outputs.digest }}
+          steps:
+            - uses: actions/checkout@v4
+            - uses: docker/setup-buildx-action@v3
+            - uses: docker/login-action@v3
+              with:
+                registry: ghcr.io
+                username: ${{ github.actor }}
+                password: ${{ secrets.GITHUB_TOKEN }}
+            - name: Build and push by digest (no tag yet)
+              id: push
+              uses: docker/build-push-action@v6
+              with:
+                push: true
+                platforms: ${{ matrix.platform }}
+                # Push by digest only — do NOT set a tag here
+                outputs: type=image,name=ghcr.io/${{ github.repository_owner }}/myapp,push-by-digest=true,name-canonical=true
+
+        merge:
+          needs: build
+          runs-on: ubuntu-latest
+          steps:
+            - uses: docker/login-action@v3
+              with:
+                registry: ghcr.io
+                username: ${{ github.actor }}
+                password: ${{ secrets.GITHUB_TOKEN }}
+            - name: Create and push multi-platform manifest
+              run: |
+                docker buildx imagetools create \
+                  -t ghcr.io/${{ github.repository_owner }}/myapp:latest \
+                  ${{ needs.build.outputs.digest }}
+                  # Merges per-platform digests into one manifest list
+prevention:
+  - "Never use strategy.matrix to build separate platforms and push to the same tag — each push overwrites the previous."
+  - "Use a single build-push-action step with comma-separated platforms for most multi-platform use cases."
+  - "Validate multi-platform images after push with `docker buildx imagetools inspect ghcr.io/owner/image:tag` to confirm all platforms are present."
+  - "When matrix builds are needed for native performance, use push-by-digest and a fan-in merge job."
+docs:
+  - url: "https://docs.docker.com/build/ci/github-actions/multi-platform/"
+    label: "Docker: Multi-platform image with GitHub Actions"
+  - url: "https://github.com/docker/build-push-action"
+    label: "docker/build-push-action — multi-platform examples"
+  - url: "https://stackoverflow.com/questions/79315376/docker-multiplatform-image-pushed-successfully-to-ghcr-but-pulling-image-result"
+    label: "SO: Docker multiplatform image pushed successfully but pulling results in manifest not found"

package/errors/silent-failures/docker-run-pipe-tee-exit-code-zero.yml

@@ -0,0 +1,99 @@
+id: silent-failures-026
+title: "Docker Run Exit Code Masked When Output Is Piped to tee"
+category: silent-failures
+severity: silent-failure
+tags:
+  - docker
+  - exit-code
+  - pipe
+  - tee
+  - bash
+  - pipefail
+patterns:
+  - regex: "docker run.*\\|.*tee"
+    flags: "i"
+  - regex: "PIPESTATUS|pipefail"
+    flags: "i"
+error_messages:
+  - "Pipe status: 0"
+  - "Exit status: 0"
+  - "The command succeeded."
+root_cause: |
+  When a `docker run` command is piped to `tee` for dual-output (file + console),
+  the shell's `$?` variable captures the exit code of the *last command in the
+  pipeline* — which is `tee`. Since `tee` always exits 0 (unless it cannot write
+  to the output file), the workflow step always reports success even when the
+  container process exits with a non-zero code.
+
+  Example:
+    docker run myimage pytest tests/ 2>&1 | tee output.txt
+    echo $?  # Always 0 — tee's exit code, not docker's
+
+  GitHub Actions enables `set -e` and `set -o pipefail` by default for bash steps,
+  but `pipefail` only propagates failures if the pipeline command itself fails.
+  When the output of `docker run` is piped, the runner still sees `tee`'s exit code
+  as the step's result.
+
+  `${PIPESTATUS[0]}` is the bash array of exit codes for each pipeline segment, but
+  it must be captured *immediately* after the pipeline — it is overwritten by the
+  next command.
+
+  Sources: stackoverflow.com/questions/79075923
+fix: |
+  Option 1 (Recommended): Capture the docker exit code via PIPESTATUS immediately
+  after the pipeline, before running any other command.
+
+  Option 2: Run docker without piping, capturing output to a variable first, then
+  echo it and write to file. This avoids the PIPESTATUS problem entirely.
+
+  Option 3: Enable `set -o pipefail` in the step shell (note: GitHub Actions bash
+  steps do NOT enable pipefail by default despite documentation implying otherwise —
+  test explicitly).
+fix_code:
+  - language: yaml
+    label: "Capture docker exit code via PIPESTATUS[0]"
+    code: |
+      - name: Run tests in Docker
+        run: |
+          docker run myimage pytest tests/ 2>&1 | tee output.txt
+          DOCKER_EXIT=${PIPESTATUS[0]}
+          # PIPESTATUS must be captured immediately after the pipeline
+          echo "Docker exit code: $DOCKER_EXIT"
+          if [ "$DOCKER_EXIT" -ne 0 ]; then
+            echo "Tests failed inside container."
+            exit "$DOCKER_EXIT"
+          fi
+  - language: yaml
+    label: "Avoid piping: capture output in variable, then write and echo"
+    code: |
+      - name: Run tests in Docker
+        run: |
+          # Capture output without piping — preserves $? correctly
+          docker_output=$(docker run myimage pytest tests/ 2>&1)
+          DOCKER_EXIT=$?
+          echo "$docker_output"          # Show in Actions log
+          echo "$docker_output" > output.txt  # Also write to file
+          if [ "$DOCKER_EXIT" -ne 0 ]; then
+            echo "Tests failed (exit $DOCKER_EXIT)"
+            exit "$DOCKER_EXIT"
+          fi
+  - language: yaml
+    label: "Use process substitution to write to file without a pipeline"
+    code: |
+      - name: Run tests in Docker
+        run: |
+          # tee via process substitution — preserves docker's exit code
+          docker run myimage pytest tests/ 2>&1 > >(tee output.txt)
+          # $? is now docker's exit code, not tee's
+prevention:
+  - "Never check $? after a piped command to determine success — always use ${PIPESTATUS[0]} or avoid piping."
+  - "Add an explicit exit-code check after any docker run step, especially when the step uses | tee or redirections."
+  - "Consider adding `set -o pipefail` at the top of multi-command run steps to catch pipeline failures automatically."
+  - "Test workflows with a deliberately failing container command to confirm the step actually fails as expected."
+docs:
+  - url: "https://www.gnu.org/software/bash/manual/bash.html#index-PIPESTATUS"
+    label: "Bash manual — PIPESTATUS"
+  - url: "https://stackoverflow.com/questions/79075923/how-can-i-get-the-error-codes-in-github-actions-shell-when-a-docker-run-command"
+    label: "SO: Get error codes in github-actions shell when docker run command fails while piping output"
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions"
+    label: "GitHub Actions workflow commands"

package/package.json

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