Skip to content

docs(tekton): a PR red your diff cannot reach is INHERITED β€” measured 3x in one session, on 3 legs - #1183

Open
ZacxDev wants to merge 1 commit into
mainfrom
docs/tekton-inherited-red
Open

docs(tekton): a PR red your diff cannot reach is INHERITED β€” measured 3x in one session, on 3 legs#1183
ZacxDev wants to merge 1 commit into
mainfrom
docs/tekton-inherited-red

Conversation

@ZacxDev

@ZacxDev ZacxDev commented Aug 31, 2026

Copy link
Copy Markdown
Member

Routed here by /handoff step 4. The subsystem-index windows returned no-match (the work landed as PRs authored in throwaway worktrees, and the only nomination was a generic scripts slug covering two unrelated paths), so the durable lesson belongs in the skill that owns the gate rather than in a per-topic handoff doc that gets overwritten.

Measured three times in one session, on three different legs

All on ZacxDev/homelab-infra, 2026-08-31:

leg what happened
gitleaks docs-only diff. Trunk itself had been red ~5 h since e097d136, on another session's handoff quoting password: "changeme-clickhouse-password"
sops-rules rule count DROPPED: 33 β†’ 32, naming a rule the branch never touched β€” trunk added it after the branch point
scripts-tests docs-only diff; trunk was broken and c902cdd5 ("unbreak trunk CI") fixed it after branching

The tell is constant: a failing leg your diff cannot touch. The control is base-vs-branch β€” run the same leg against origin/trunk and compare; identical output proves the red is not yours. Then rebase; don't debug the leg.

Two things that cost real time

  • πŸ”΄ Trunk can be red for hours while every open PR still looks green, because they all branched before the offending commit. A green PR is evidence about its branch point, never about trunk. Nothing currently watches trunk's own gate state.
  • ⚠ gh pr checks reports "no checks reported" for a PR with a passing commit status β€” Tekton posts a legacy status, not a check-run. Use gh api repos/<o>/<r>/commits/<sha>/status.

The gitleaks instance was fixed in homelab-infra#598 with a rule-scoped [[rules.allowlists]] exempting ^claudedocs/ from unrotated-template-default only β€” a global [[allowlists]] paths entry would have exempted those files under every rule.

πŸ€– Generated with Claude Code

https://claude.ai/code/session_01UGspsNfAdDqeD74yFvYzDa

… 3x in one session, on 3 legs

Routed here by /handoff step 4: the subsystem-index windows came back no-match
(the work landed as PRs from throwaway worktrees, and the nominated slug was a
generic `scripts`), so the durable lesson belongs in the skill that owns the
gate rather than in a per-topic handoff doc that gets overwritten.

All three on ZacxDev/homelab-infra, 2026-08-31:

  gitleaks       docs-only diff; TRUNK ITSELF had been red ~5h since e097d136 on
                 another session's handoff QUOTING `password: "changeme-..."`.
                 Fixed by #598 -- a rule-scoped [[rules.allowlists]] exempting
                 ^claudedocs/ from unrotated-template-default ONLY (global
                 [[allowlists]] paths would exempt the file under EVERY rule)
  sops-rules     `rule count DROPPED: 33 -> 32` naming a rule the branch never
                 touched -- trunk ADDED it after the branch point
  scripts-tests  docs-only diff; trunk was broken and c902cdd5 fixed it after
                 branching

The tell is constant: a failing leg the diff cannot touch. The control is
base-vs-branch -- run the leg against origin/trunk and compare. Then REBASE.

Also records two things that cost real time:
  * trunk can be red for HOURS while every open PR looks green, because they all
    branched earlier. A green PR is evidence about its branch point, not trunk
  * `gh pr checks` says "no checks reported" for a PR with a PASSING commit
    status -- Tekton posts a legacy status, not a check-run

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UGspsNfAdDqeD74yFvYzDa
Claude-Session-Id: f1f6b2ed-d8ca-4830-b379-5e19f7222460
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant