aio-libs/aiohttp

Implement automation closing PRs and issues where the OP does not follow the expected template

Closed

#12,163 opened on Feb 27, 2026

View on GitHubContributor guide
 (30 comments) (0 reactions) (2 assignees)Python (1,997 forks)batch import
Hacktoberfestenhancementgithub_actionsgood first issueinframetaneed pull request

Repository metrics

Stars
 (14,286 stars)
PR merge metrics
 (Avg merge 5d 2h) (198 merged PRs in 30d)

Description

Is your feature request related to a problem?

There's a lot of slop and this will hopefully encourage people think before posting.

Describe the solution you'd like

SSIA. It should be possible to implement a PoC based on GHA.

Describe alternatives you've considered

Closing spam manually.

Related component

GH Repo

Additional context

Examples of PRs not following the templates can be easily found among the recently closed ones. The templates are under .github/.

Code of Conduct

  • I agree to follow the aio-libs Code of Conduct

Contributor guide

Research direction
Examine the issue templates under .github/ and design a GitHub Action that checks if the body starts with the template structure. Use actions/github script or a Python script to parse and validate.
Tech stack
python
Domain
devopsdeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65