Skip to content

Correct PR hygiene trust-boundary and policy-history comments #8388

Open

Description

@lidge-jun

Documentation problem type

Incorrect documentation

Documentation location

.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.

Checks

  • I searched existing documentation issues.
  • No secrets or personal information are included.

Activity

  1. coderabbitai commented on Nov 8, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #8381 - chore: remove retired release branch references [open]


    📝 Issue Planner

    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!

  2. MannXo commented on Nov 9, 2026

    @MannXo
    Contributor

    I'm interested in picking this up. Happy to discuss approach if needed.

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

    documentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions