Skip to content
Check for Spammy PRs

Clarify ambiguous precedence for org-level and repo-level PR limits #646

Sign in to view logs

Clarify ambiguous precedence for org-level and repo-level PR limits

Clarify ambiguous precedence for org-level and repo-level PR limits #646

Triggered via pull request October 28, 2026 11:16
@hugovkhugovk
synchronize #46517
Status Success
Total duration 11s
Artifacts –

check-for-spammy-prs.yml

on: pull_request_target
Close PRs with emoji titles
4s
Close PRs with emoji titles
Label spammy PRs and reject non-main targets
6s
Label spammy PRs and reject non-main targets
Fit to window
Zoom out
Zoom in

Annotations

1 warning and 2 notices
Workflow execution policy warning (evaluate mode): .github/workflows/check-for-spammy-prs.yml#L1
On December 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target
Close PRs with emoji titles
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Label spammy PRs and reject non-main targets
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"