Skip to content

feat: add automated spam detection workflow #13893

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

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat: add automated spam detection workflow #13893

wants to merge 2 commits into from
+157 −0

Conversation

@natthapolvanasrivilai
Copy link

@natthapolvanasrivilai natthapolvanasrivilai commented Nov 27, 2025

This PR introduces a new GitHub Actions workflow gemini-spam-detection.yml that uses the Gemini CLI to automatically detect and manage spam issues.

Features:

  • Triggers: issues (opened, reopened, edited) and workflow_dispatch (manual trigger).
  • Analysis: Uses Gemini to analyze the issue title and body against a set of spam definitions (ads, gibberish, etc.).
  • Action: If identified as spam:
    • Adds spam label.
    • Closes the issue with reason not_planned.
    • Adds a comment explaining the closure.

This automation will help reduce the manual toil of closing spam issues.

@natthapolvanasrivilai natthapolvanasrivilai requested a review from a team as a code owner November 27, 2025 05:57
@gemini-code-assist
Copy link
Contributor

gemini-code-assist bot commented Nov 27, 2025

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@natthapolvanasrivilai natthapolvanasrivilai force-pushed the feat/spam-detection-workflow branch from 310f942 to cd9bfe4 Compare November 27, 2025 05:59
@natthapolvanasrivilai
Copy link
Author

natthapolvanasrivilai commented Nov 27, 2025

Hi!

I've checked the status of the Pull Request (#13893). It appears that the CI checks (like linting and unit tests) should automatically run for PRs from forks. However, the status currently shows total_count: 0 which indicates no checks have been registered yet. This might be a temporary delay on GitHub's side.

Regarding the E2E tests, I found in the e2e.yml workflow that these tests only run for PRs from forks if a maintainer adds the label maintainer:e2e:ok.

Could you please add the maintainer:e2e:ok label to this PR so the E2E checks can start?

In the meantime, I'll also try commenting on the PR, as sometimes this can re-trigger checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@natthapolvanasrivilai