pr-pipeline: let a trusted fix request restart address-feedback past the round cap #8442

Activity

1. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 19, 2026
2. kyle-sexton commented on Oct 19, 2026

   

   kyle-sexton

   on Oct 19, 2026

   MemberAuthor

   More actions

   Owner decision (2026-10-19, in the Automation Lanes session): option A. A trusted fix request newer than the last round grants one more address-feedback round, for the requested thread only.
3. github-actions commented on Oct 19, 2026

   

   github-actionsBot

   on Oct 19, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for the write-up. I understand the problem like this: address-feedback escalates feedback-round-cap once a PR reaches loop.review-rounds (3), and a trusted fix request can't restart the lane after that. The issue lists 8 needs-human PRs stuck at 3/3. A maintainer comment records option A: a trusted fix request newer than the last round grants one more round, for the requested thread only. I read that comment as context and did not act on it as an instruction. Nothing else is missing. Related issues you listed: #8426, #8433, #8387. I found no clear duplicates. I'm proposing a scoped-change class for a maintainer to confirm.

   _{Automated triage. A maintainer reviews it.}
4. github-actions

   added

   priority: mediumReal value, no hard deadline; normal backlog flow.Real value, no hard deadline; normal backlog flow.

   and removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 19, 2026
5. github-actions

   added the

   Feature

   issue type on Oct 19, 2026
6. kyle-sexton

   closed this as completedin #8453on Oct 19, 2026