Repository navigation
Description
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_TOKENis empty on Dependabot-triggered runs;gh auth statusexits 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 pipefailscript immediately afteractions/cacherestore; this is the token-validation preflight inpr-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 passessecrets: inheritto 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 toGH_TOKENinpr-review.yml— is absent.ghfinds no token, reports "not logged in," and the preflight exits 1. - Scope-check code never reached: The fine-grained PAT detection and
repo/read:orgscope validation are downstream of the failinggh auth statusguard — 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. AddDON_PETRY_BOT_GH_PATunder Settings → Secrets and variables → Dependabot. No code change required.- Alternative: add an
if: github.actor != 'dependabot[bot]'condition to thereviewjob inpr-review.yml(or in this trigger stub's job) so Dependabot PRs are silently skipped rather than failing.
5. Recommendations
-
[CRITICAL] Add
DON_PETRY_BOT_GH_PATto Dependabot secrets- What: In GitHub org/repo Settings → Secrets and variables → Dependabot, add
DON_PETRY_BOT_GH_PATwith 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
- What: In GitHub org/repo Settings → Secrets and variables → Dependabot, add
-
[HIGH] Add a Dependabot skip guard as defense-in-depth
- What: In
pr-review.yml(at the reusable workflow level,pr-review/stabletag), addif: github.actor != 'dependabot[bot]'on thereviewjob, or emit a clear::notice::andexit 0in the preflight whenGH_TOKENis unset - Why: Even with fix test issue from agent #1, future secret rotation gaps or new Dependabot contexts will produce cryptic
gh authfailures; a guard gives an actionable skip message instead - Expected impact: Turns credential-absent runs from
failuretoskippedwith a clear reason; prevents alert fatigue - Urgency: HIGH — reduces blast radius of future credential issues
- What: In
-
[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
- What: Check the concurrency group configuration in
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
don-petry commentedon Jul 14, 2026
Closing stale daily digest — superseded by the newest snapshot. Digest steps now close prior days automatically (#1204 / #1212).