Hacktoberfest From the Maintainer's Side: Faster PR Closing

说明与用途

在 Hacktoberfest 期间的自动化和政策变更将 triage 时间减少 60%，降低了垃圾邮件，提高了真实贡献的审查速度。

问题

During Hacktoberfest the repo received 380 PRs in three weeks, overwhelming maintainers and causing 60% triage time increase.

结果

Automation and policy changes cut triage time by ~60 % and reduced spam, improving review speed for genuine contributors.

工作流

• Create GitHub Action that runs on pull_request events
• Compute diff stats (files changed, lines changed)
• Detect trivial-only changes (no src/lib files touched)
• Apply labels: low‑signal, large‑diff
• Add bot checks: linked issue required, account age heuristic, duplicate good‑first‑issue detection
• Close PRs with templated message if spam:likely or low‑signal without linked issue
• Adjust repo Hacktoberfest topic to control spam influx

证据

Last Hacktoberfest, our repo (a mid-sized CLI tool with about 4k stars) got hit with 380 pull requests in three weeks.

来源

That second and third category is what pushed us to change our process mid-month.

来源

We built a GitHub Action that runs on every pull_request event and does a first-pass triage before a human ever looks at it.

来源

Median time-to-first-response dropped from 36 hours to 4 hours

来源

We did get a handful of complaints about the terse closing message — a fair trade-off in our view

来源