@htekdev/actions-debugger 1.0.85 → 1.0.86

package/errors/caching-artifacts/upload-artifact-storage-quota-exceeded.yml

@@ -0,0 +1,76 @@
+id: caching-artifacts-050
+title: "upload-artifact@v4 fails when artifact storage quota is exceeded"
+category: caching-artifacts
+severity: error
+tags:
+  - upload-artifact
+  - storage-quota
+  - v4
+  - billing
+  - artifact-cleanup
+patterns:
+  - regex: 'Artifact storage quota has been hit'
+    flags: i
+  - regex: 'unable to upload any new artifacts'
+    flags: i
+  - regex: 'storage limit.*exceeded'
+    flags: i
+error_messages:
+  - "Artifact storage quota has been hit, unable to upload any new artifacts. Please remove some old artifacts or increase storage for the repo."
+root_cause: |
+  GitHub Actions artifact storage has per-account limits (500 MB for free plans, 2 GB for Pro,
+  50 GB for Teams, and custom limits for Enterprise). Unlike actions/upload-artifact@v3 which
+  used a legacy backend, v4 strictly enforces storage quotas and fails hard when the limit
+  is exceeded. Old artifacts from previous workflow runs accumulate over time and are not
+  automatically purged unless a retention policy is set. Once the quota is hit, all subsequent
+  artifact uploads fail immediately with no partial upload.
+fix: |
+  1. Set retention-days on all upload-artifact steps to automatically expire old artifacts.
+  2. Delete old artifacts programmatically using the GitHub REST API via actions/github-script.
+  3. Increase artifact and log storage in GitHub billing settings (Org/User Settings -> Billing -> Storage).
+  4. Audit artifact size — only upload what is necessary for debugging or downstream jobs.
+fix_code:
+  - language: yaml
+    label: "Set retention-days to auto-expire artifacts"
+    code: |
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: build-output
+          path: dist/
+          retention-days: 7   # auto-delete after 7 days; default is 90
+
+  - language: yaml
+    label: "Delete artifacts older than 30 days via GitHub API script"
+    code: |
+      - name: Clean up old artifacts
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const cutoff = new Date();
+            cutoff.setDate(cutoff.getDate() - 30);
+            const artifacts = await github.paginate(
+              github.rest.actions.listArtifactsForRepo,
+              { owner: context.repo.owner, repo: context.repo.repo, per_page: 100 }
+            );
+            for (const artifact of artifacts) {
+              if (new Date(artifact.created_at) < cutoff) {
+                await github.rest.actions.deleteArtifact({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  artifact_id: artifact.id,
+                });
+              }
+            }
+prevention:
+  - "Always set retention-days on upload-artifact steps — default is 90 days which fills storage quickly"
+  - "Upload only the minimum files needed for debugging or downstream jobs, not entire build directories"
+  - "Add a weekly scheduled workflow to delete artifacts older than your retention window"
+  - "Monitor storage usage under GitHub Settings -> Billing & plans -> Storage"
+docs:
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/storing-workflow-data-as-artifacts#configuring-a-custom-artifact-retention-period"
+    label: "GitHub Docs: Custom artifact retention period"
+  - url: "https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-github-actions/about-billing-for-github-actions#included-storage-and-minutes"
+    label: "GitHub Docs: Included storage and minutes"
+  - url: "https://github.com/actions/upload-artifact/issues/577"
+    label: "actions/upload-artifact#577: Storage quota exceeded on v4"

package/errors/permissions-auth/fine-grained-pat-resource-owner-mismatch.yml

@@ -0,0 +1,75 @@
+id: permissions-auth-050
+title: "Fine-grained PAT with wrong resource owner causes 'repository not found' in checkout"
+category: permissions-auth
+severity: error
+tags:
+  - fine-grained-pat
+  - checkout
+  - resource-owner
+  - PAT
+  - authentication
+patterns:
+  - regex: 'repository.*not found'
+    flags: i
+  - regex: 'remote: Repository not found'
+    flags: i
+  - regex: 'fatal: unable to access.*403'
+    flags: i
+error_messages:
+  - "fatal: repository 'https://github.com/org/repo.git/' not found"
+  - "remote: Repository not found."
+  - "Error: fatal: unable to access 'https://github.com/org/repo.git/': The requested URL returned error: 403"
+root_cause: |
+  Fine-grained personal access tokens (PATs) require selecting a resource owner when created —
+  either your personal account or a specific organization. A token scoped to a personal account
+  (e.g., user alice) cannot authenticate to repositories owned by an organization (e.g., myorg),
+  even if alice is a member of myorg with full access. Attempting to use such a PAT in
+  actions/checkout, actions/github-script REST calls, or any GitHub API call targeting the
+  organization's repos results in a misleading "repository not found" or HTTP 403 error. The
+  repository is accessible through the web UI because browser sessions use OAuth-based auth —
+  but the fine-grained PAT token is strictly limited to its configured resource owner scope.
+  Classic PATs (without granular resource scope) do not have this restriction, which is why
+  the problem only appears after migrating to fine-grained PATs.
+fix: |
+  Regenerate the fine-grained PAT selecting the correct resource owner — the organization or
+  user account that owns the target repository. If you need to access repositories across
+  multiple organizations, create one PAT per organization, or use a GitHub App installation
+  token which supports cross-repo access without resource-owner restrictions.
+fix_code:
+  - language: yaml
+    label: "Checkout org repo — PAT must have org as resource owner"
+    code: |
+      # The secret ORG_SCOPED_PAT must be a fine-grained PAT created with
+      # Resource owner = myorg (not your personal account)
+      - uses: actions/checkout@v4
+        with:
+          repository: myorg/private-repo
+          token: ${{ secrets.ORG_SCOPED_PAT }}
+
+  - language: yaml
+    label: "Use a GitHub App installation token to avoid resource-owner scope issues"
+    code: |
+      - name: Generate app installation token
+        id: app-token
+        uses: actions/create-github-app-token@v2
+        with:
+          app-id: ${{ vars.APP_ID }}
+          private-key: ${{ secrets.APP_PRIVATE_KEY }}
+          owner: myorg
+
+      - uses: actions/checkout@v4
+        with:
+          repository: myorg/private-repo
+          token: ${{ steps.app-token.outputs.token }}
+prevention:
+  - "When creating a fine-grained PAT, verify the Resource owner dropdown matches the organization or user that OWNS the target repository"
+  - "Name secrets descriptively: ORG_SCOPED_PAT vs USER_SCOPED_PAT to avoid mixing tokens with different owners"
+  - "Prefer GitHub App installation tokens for multi-repo or cross-org access — they have no resource-owner scoping restriction"
+  - "Classic PATs (repo scope) remain an option if fine-grained token resource-owner scoping is causing confusion"
+docs:
+  - url: "https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token"
+    label: "GitHub Docs: Creating a fine-grained personal access token"
+  - url: "https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#about-fine-grained-personal-access-tokens"
+    label: "GitHub Docs: About fine-grained PATs and resource owner scope"
+  - url: "https://github.com/actions/checkout?tab=readme-ov-file#checkout-a-different-private-repository"
+    label: "actions/checkout: Checkout a different private repository"

package/errors/runner-environment/github-script-require-relative-path-cwd.yml

@@ -0,0 +1,74 @@
+id: runner-environment-150
+title: "actions/github-script relative require() fails — CWD is not GITHUB_WORKSPACE"
+category: runner-environment
+severity: error
+tags:
+  - github-script
+  - require
+  - nodejs
+  - working-directory
+  - module-not-found
+patterns:
+  - regex: 'Cannot find module'
+    flags: i
+  - regex: 'MODULE_NOT_FOUND'
+    flags: ''
+error_messages:
+  - "Error: Cannot find module './my-helper'"
+  - "Error: Cannot find module '../utils/helper'"
+  - "{ code: 'MODULE_NOT_FOUND' }"
+root_cause: |
+  The actions/github-script action evaluates the script: block in a Node.js context where the
+  current working directory (CWD) is a temporary internal directory used by the action runtime —
+  NOT $GITHUB_WORKSPACE. As a result, relative require() calls like require('./helpers/my-util')
+  fail with "Cannot find module" even when the file exists in the repository workspace. This
+  surprises developers who assume the script evaluates from the repository root directory.
+  Note: This is distinct from missing npm packages (runner-environment-136) — the file exists
+  on disk but is not found because Node.js resolves the relative path from the wrong base directory.
+fix: |
+  Construct an absolute path using process.env.GITHUB_WORKSPACE before calling require(). The
+  GITHUB_WORKSPACE environment variable is always set to the repository root in hosted runners.
+  Alternatively, use the recommended pattern from the actions/github-script docs: point to the
+  absolute path via a template literal.
+fix_code:
+  - language: yaml
+    label: "Use absolute path via process.env.GITHUB_WORKSPACE"
+    code: |
+      - uses: actions/github-script@v7
+        with:
+          script: |
+            const myHelper = require(`${process.env.GITHUB_WORKSPACE}/scripts/my-helper.js`);
+            await myHelper.run(github, context);
+
+  - language: yaml
+    label: "Pass workspace as env var for explicit clarity"
+    code: |
+      - uses: actions/github-script@v7
+        env:
+          WORKSPACE: ${{ github.workspace }}
+        with:
+          script: |
+            const helper = require(`${process.env.WORKSPACE}/scripts/helper.js`);
+            const result = helper.compute();
+            core.setOutput('result', result);
+
+  - language: yaml
+    label: "Use path.resolve for cross-platform safety"
+    code: |
+      - uses: actions/github-script@v7
+        with:
+          script: |
+            const path = require('path');
+            const utils = require(path.resolve(process.env.GITHUB_WORKSPACE, 'lib', 'utils.js'));
+            utils.run();
+prevention:
+  - "Never use relative require() paths in github-script — always construct absolute paths with process.env.GITHUB_WORKSPACE"
+  - "Print process.cwd() in debug runs to confirm the actual CWD — it will not be your repo root"
+  - "For complex shared logic, consider a composite action or a dedicated JS action that has proper module resolution"
+docs:
+  - url: "https://github.com/actions/github-script?tab=readme-ov-file#run-a-separate-file"
+    label: "actions/github-script: Run a separate file (recommended pattern)"
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#default-environment-variables"
+    label: "GitHub Docs: GITHUB_WORKSPACE default environment variable"
+  - url: "https://github.com/actions/github-script/issues/390"
+    label: "actions/github-script#390: Cannot find module with relative path"

package/errors/silent-failures/checkout-path-github-workspace-unchanged.yml

@@ -0,0 +1,91 @@
+id: silent-failures-079
+title: "actions/checkout path: input doesn't change GITHUB_WORKSPACE — subsequent steps use wrong directory"
+category: silent-failures
+severity: silent-failure
+tags:
+  - checkout
+  - path
+  - GITHUB_WORKSPACE
+  - working-directory
+  - subdirectory
+patterns:
+  - regex: 'No such file or directory'
+    flags: i
+  - regex: 'ENOENT.*no such file'
+    flags: i
+error_messages:
+  - "No such file or directory"
+  - "ENOENT: no such file or directory"
+root_cause: |
+  When actions/checkout is used with a path: input (e.g., path: app), the repository is
+  checked out into $GITHUB_WORKSPACE/app. However, the GITHUB_WORKSPACE environment variable
+  continues to point to the root workspace directory (/home/runner/work/repo-name/repo-name),
+  not to the path: subdirectory. Any subsequent run: steps that use ${{ github.workspace }}
+  or rely on the default working directory will NOT operate inside the checkout subdirectory.
+  This causes file-not-found errors that are hard to debug because the checkout step succeeds
+  and the files do exist — just not at the location subsequent steps expect. This is a
+  particularly common footgun when checking out multiple repositories into different subdirs.
+fix: |
+  Explicitly specify working-directory on all run: steps that operate on the checked-out code,
+  OR set a job-level defaults.run.working-directory. Alternatively, avoid path: unless you
+  need multiple checkouts — the default checkout places files directly at $GITHUB_WORKSPACE.
+fix_code:
+  - language: yaml
+    label: "Use working-directory to point to the checkout subdirectory"
+    code: |
+      - uses: actions/checkout@v4
+        with:
+          path: app
+
+      - name: Build
+        working-directory: ${{ github.workspace }}/app
+        run: npm install && npm run build
+
+  - language: yaml
+    label: "Set job-level default working-directory"
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          defaults:
+            run:
+              working-directory: ./app
+          steps:
+            - uses: actions/checkout@v4
+              with:
+                path: app
+            - run: npm install && npm run build
+
+  - language: yaml
+    label: "Multiple checkouts — use explicit paths for each"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+          with:
+            repository: myorg/frontend
+            path: frontend
+
+        - uses: actions/checkout@v4
+          with:
+            repository: myorg/backend
+            path: backend
+
+        - name: Build frontend
+          working-directory: frontend
+          run: npm ci && npm run build
+
+        - name: Build backend
+          working-directory: backend
+          run: go build ./...
+prevention:
+  - "Prefer the default checkout (no path:) unless checking out multiple repos in the same job"
+  - "When path: is used, always add defaults.run.working-directory at the job level"
+  - "Never use ${{ github.workspace }} to reference files from a path:-redirected checkout without appending the path value"
+  - "Use echo $GITHUB_WORKSPACE and ls $GITHUB_WORKSPACE in debug steps to verify directory contents"
+docs:
+  - url: "https://github.com/actions/checkout?tab=readme-ov-file#usage"
+    label: "actions/checkout: path input documentation"
+  - url: "https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun"
+    label: "GitHub Docs: jobs.defaults.run.working-directory"
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#default-environment-variables"
+    label: "GitHub Docs: GITHUB_WORKSPACE default environment variable"

package/package.json

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