Skip to content

PR Review Agent — failures detected 2026-06-20 #830

Closed

Description

@github-actions

1. Executive Summary

Status: DEGRADED
Period: 2026-06-20T06:55:43Z – 2026-06-20T07:07:08Z
Result: 2 of 40 actionable runs failed (5%) — 53 cancelled (53%), 7 skipped

Key findings:

  • All 2 failures share one root cause: GH_TOKEN is empty on Dependabot-triggered runs; gh auth status exits 1 before any review logic executes
  • Both failed runs targeted the same PR (chore(deps): bump the actions group across 1 directory with 7 updates #808), both show Secret source: Dependabot — Dependabot PRs cannot access org/repo secrets by default
  • 53% cancellation rate is structurally elevated but expected for a high-velocity burst (~100 runs in 11 min); likely driven by concurrency-group preemption in the reusable workflow

Action required: Grant Dependabot access to DON_PETRY_BOT_GH_PAT (via repo Settings → Secrets → Dependabot secrets) or add a workflow-level guard to skip review for Dependabot PRs.


2. Failure Breakdown

Failure Category Affected Runs Example Error Message
Missing auth token (Dependabot secret isolation) #31383, #31302 You are not logged into any GitHub hosts. To log in, run: gh auth login

3. Error Patterns

Category: Missing auth token — Dependabot secret isolation

Exact error (both runs):

You are not logged into any GitHub hosts. To log in, run: gh auth login
##[error]gh auth status failed
##[error]Process completed with exit code 1.
  • Step: Inline set -euo pipefail script immediately after actions/cache restore; this is the token-validation preflight in pr-review.yml
  • What the script does: Runs gh auth status 2>&1; if it fails it prints the output and exits
  • Root cause: GH_TOKEN: is blank in both failed runs (visible in the env dump). The calling trigger stub passes secrets: inherit to the reusable, but when a Dependabot event fires the workflow, GitHub does not inject repository/organization secrets into the job. DON_PETRY_BOT_GH_PAT — which maps to GH_TOKEN in pr-review.yml — is absent. gh finds no token, reports "not logged in," and the preflight exits 1.
  • Scope-check code never reached: The fine-grained PAT detection and repo/read:org scope validation are downstream of the failing gh auth status guard — they never execute.

4. Token Scope Analysis

Item Detail
Secret source on failed runs Dependabot (logged by runner at job start)
GH_TOKEN value in failed env (empty string)
Scopes present None — token absent entirely
Scopes required (per preflight script) Classic PAT: repo + read:org; OR fine-grained: contents + pull_requests:write
Scopes missing All — token never injected

Recommendation per missing scope:

  • GH_TOKEN (any scope) — Root issue. Dependabot workflows cannot read standard repo/org secrets unless explicitly added to the Dependabot secrets store. Add DON_PETRY_BOT_GH_PAT under Settings → Secrets and variables → Dependabot. No code change required.
  • Alternative: add an if: github.actor != 'dependabot[bot]' condition to the review job in pr-review.yml (or in this trigger stub's job) so Dependabot PRs are silently skipped rather than failing.

5. Recommendations

  1. [CRITICAL] Add DON_PETRY_BOT_GH_PAT to Dependabot secrets

    • What: In GitHub org/repo Settings → Secrets and variables → Dependabot, add DON_PETRY_BOT_GH_PAT with the same value as the Actions secret
    • Why: Dependabot-triggered jobs cannot access Actions secrets; the token is absent, causing 100% failure for Dependabot PR events
    • Expected impact: Eliminates both failure categories; Dependabot PRs will be reviewed normally
    • Urgency: CRITICAL — every Dependabot PR currently produces a failed workflow run
  2. [HIGH] Add a Dependabot skip guard as defense-in-depth

    • What: In pr-review.yml (at the reusable workflow level, pr-review/stable tag), add if: github.actor != 'dependabot[bot]' on the review job, or emit a clear ::notice:: and exit 0 in the preflight when GH_TOKEN is unset
    • Why: Even with fix test issue from agent #1, future secret rotation gaps or new Dependabot contexts will produce cryptic gh auth failures; a guard gives an actionable skip message instead
    • Expected impact: Turns credential-absent runs from failure to skipped with a clear reason; prevents alert fatigue
    • Urgency: HIGH — reduces blast radius of future credential issues
  3. [LOW] Investigate elevated cancellation rate (53%)

    • What: Check the concurrency group configuration in pr-review.yml@pr-review/stable; confirm whether the 53% cancellation rate during this burst is intentional preemption or unexpected queuing behavior
    • Why: 53 cancels in 11 minutes suggests either a mass-sync event (rebase touching many PRs) or a concurrency limit that is too aggressive; if the latter, reviews may be silently skipped
    • Expected impact: Better visibility into whether PRs are actually being reviewed or silently dropped
    • Urgency: LOW — cancels are not failures, but a spike this large warrants a one-time audit

6. Health Score

Health: 7/10 — Structurally sound with a single reproducible Dependabot secret isolation failure that is blocking all Dependabot PR reviews and is fixable with a one-time secrets configuration change.

Activity

  1. don-petry commented on Jul 14, 2026

    @don-petry
    Collaborator

    Closing stale daily digest — superseded by the newest snapshot. Digest steps now close prior days automatically (#1204 / #1212).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    automated-reportCreated by automated workflowhealth-checkAutomated health check report

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions