gocolly/colly

How should we handle these DDoS AI contributions?

Open

#920 opened on Jun 18, 2026

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Go (1,854 forks)batch import
help wantedquestion

Repository metrics

Stars
 (25,403 stars)
PR merge metrics
 (Avg merge 15h 38m) (2 merged PRs in 30d)

Description

First of all, we should create a contribution guide where we specify the preferred way to create AI aided contributions. I suggest this as a base: https://github.com/asciimoo/hister/blob/master/CONTRIBUTING.md#ai-policy

Second, we have tons of opened PRs by AI. Should we close all without reviews?

@WGH- , everyone what do you think?

Contributor guide

Research direction
Read the proposed AI policy from the linked repository, review the existing AI generated pull requests to assess their quality, and share your thoughts in the issue discussion.
Tech stack
go
Domain
backenddeveloper experience
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70