Skip to content

fix: make anti-slop advisory instead of auto-closing legitimate PRs #741

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
anandgupta42 merged 1 commit into from
Apr 23, 2026
Merged

fix: make anti-slop advisory instead of auto-closing legitimate PRs #741

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion .github/workflows/anti-slop.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,13 @@ jobs:
master
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot Apr 23, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: Update the failure message to match the new advisory behavior; it still tells contributors the PR was automatically closed even though closure is now disabled.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/anti-slop.yml, line 86:

<comment>Update the failure message to match the new advisory behavior; it still tells contributors the PR was automatically closed even though closure is now disabled.</comment>

<file context>
@@ -77,7 +77,13 @@ jobs:
+          # blocked-terms check and gets closed 2 minutes after opening. The
+          # labels and failure message still fire, so maintainers retain the
+          # signal and can close manually when warranted. See issue #740.
+          close-pr: false
           lock-pr: false
           failure-add-pr-labels: "needs-review:blocked"
</file context>
Fix with Cubic


# --- Actions on failure ---
close-pr: true
# Advisory, not blocking. Too many legitimate team PRs were auto-closed
# because the PR template instructs LLMs to prepend "PINEAPPLE"
# (honeypot) — any AI-assisted PR from a team member then trips the
# blocked-terms check and gets closed 2 minutes after opening. The
# labels and failure message still fire, so maintainers retain the
# signal and can close manually when warranted. See issue #740.
close-pr: false
lock-pr: false
failure-add-pr-labels: "needs-review:blocked"
failure-pr-message: |
Expand Down
Loading