You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Correct PR hygiene trust-boundary and policy-history comments #8388
.github/workflows/pr-hygiene.yml header and devlog/_plan/261108_dev_single_branch_release/020_stale_branch_cleanup.md.
What is wrong or missing?
The hygiene workflow header describes loading trusted scripts from the PR base revision, while the checkout in PR #8381 uses the fixed dev ref. The cleanup plan also attributes an evidence-policy drift repair to that PR, although the earlier dev policy already covers the relevant workflow revision.
What should the documentation explain instead?
Describe the fixed trusted checkout accurately and correct the history of the evidence-policy entry.
Suggested wording or example
State that privileged PR hygiene loads trusted scripts from dev, and distinguish the new workflow fingerprint from previously repaired policy drift.
Additional context or attachments
Follow-up to the independent technical review of PR #8381 at 32818c2209ff054968ed28b5cdebcd0cee078b26.
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Nov 8, 2026
🔗 Related PRs
#8381 - chore: remove retired release branch references [open]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
MannXo commentedon Nov 9, 2026
I'm interested in picking this up. Happy to discuss approach if needed.