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
fix\(pr-pipeline\): align every needs-human path with the owner stop rule - part 2 of 6 #11020
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: babysit_risk.person_reasons escalates only a CRITICAL security finding, but the owner stop rule says HIGH or CRITICAL. The fix is to escalate both, keep the other person reasons (high path, trusted-actor widening, file listing too long to check), and cover both severities in test_babysit_risk.py. This is part 2 of 6 of #10517. The sibling parts are separate slices, not duplicates.
Activity
github-actions commentedon Oct 29, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood:
babysit_risk.person_reasonsescalates only a CRITICAL security finding, but the owner stop rule says HIGH or CRITICAL. The fix is to escalate both, keep the other person reasons (high path, trusted-actor widening, file listing too long to check), and cover both severities intest_babysit_risk.py. This is part 2 of 6 of #10517. The sibling parts are separate slices, not duplicates.Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Oct 29, 2026
Not admitted to the issue lane yet: blocker #11019 is not closed by a listed human or a merge.