aio-libs/aiohttp

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

Open

#12,163 opened on 2026年2月27日

GitHub で見る
 (30 comments) (0 reactions) (2 assignees)Python (14,286 stars) (1,997 forks)batch import
Hacktoberfestenhancementgithub_actionsgood first issueinframetaneed pull request

説明

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

コントリビューターガイド

技術スタック
pythongithub actions
領域
devopsci cd
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
active
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
GitHub ActionsYAMLUnderstanding of issue/PR templates
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
40
調査方針
Examine existing templates under `.github/` in the aiohttp repository. Review recent closed PRs that did not follow templates to understand common violations. Then design a GitHub Actions workflow that checks the body of issues and pull requests against the expected template structure and closes them if they do not match. Consider using `actions/github script` to implement the logic. Also check the current assignees' progress on the issue to avoid duplicate work.
Implement automation closing PRs and issues where the OP does not follow the expected template · aio-libs/aiohttp#12163 | Good First Issue