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
constsummary=[run.output?.title,run.output?.summary].find((value): value is string=>typeofvalue==="string"&&value.trim().length>0)?.trim().slice(0,200);
2789
+
// security/check tool asking for human review) is a settled, terminal adverse result -- but ONLY when that
2790
+
// check is actually a REQUIRED context. A non-required third-party check must never hard-fail/auto-close the
2791
+
// PR on its own say-so: the same app can post multiple check-runs (e.g. a required "X Security Scan" plus a
2792
+
// separate, NEVER-required "X Contributor trust" advisory check), and treating either one's action_required
2793
+
// the same way conflates them (#4414 regressed exactly this -- a non-required advisory check started
2794
+
// auto-closing real contributor PRs). This is NOT the github-actions "awaiting maintainer Approve and run"
2795
+
// case the action_required exclusion above exists for: non-Actions apps use their own conclusion as a policy
2796
+
// signal. Conservative: an unknown/absent app slug is NOT treated as third-party here.
it("a third-party app's COMPLETED action_required check-run that is NOT a required context is held as a non-blocking advisory, never auto-closing the PR (#4414-regression)",async()=>{
it("a non-required third-party action_required check-run with no output/details_url still lands in nonRequiredFailingDetails, bare (name-only)",async()=>{
it("a github-actions workflow awaiting 'Approve and run' (action_required) is still treated as pending, not settled (#fork-action-required)",async()=>{
0 commit comments