.github/workflows/linked-issue.yml runs on pull_request_target with types [opened, edited, reopened, synchronize] and has no guard on the pull request's state. edited fires on a closed or merged PR too, so a body edit on a PR merged before the policy existed grades it against the policy and fails it.
That is what happened on 2026-09-14: 13 failing Linked issue policy runs in this repository, every one on a merged or closed branch, triggered by body edits on already-merged PRs. A merged PR cannot be changed to satisfy the policy, and grading it says nothing about the tree.
The open PRs in the org that currently fail this policy (other authors, in eos and ebuild) are unaffected by a state guard — the policy keeps doing its job there.
Fix: run the job only when github.event.pull_request.state == 'open'.
.github/workflows/linked-issue.ymlruns onpull_request_targetwith types[opened, edited, reopened, synchronize]and has no guard on the pull request's state.editedfires on a closed or merged PR too, so a body edit on a PR merged before the policy existed grades it against the policy and fails it.That is what happened on 2026-09-14: 13 failing
Linked issue policyruns in this repository, every one on a merged or closed branch, triggered by body edits on already-merged PRs. A merged PR cannot be changed to satisfy the policy, and grading it says nothing about the tree.The open PRs in the org that currently fail this policy (other authors, in
eosandebuild) are unaffected by a state guard — the policy keeps doing its job there.Fix: run the job only when
github.event.pull_request.state == 'open'.