aio-libs/aiohttp

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

Open

#12,163 建立於 2026年2月27日

在 GitHub 查看
 (30 留言) (0 反應) (2 負責人)Python (14,286 star) (1,997 fork)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
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.