Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Single-source the public-surface mypy gate in `[tool.mypy]` instead of four hand-copied flag strings

未关闭
#919 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
62/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
python

调研方向

Start in pyproject.toml, which has no [tool.mypy] section yet, and copy the current gate flags and files from ci.yml, CLAUDE.md, AGENTS.md and CONTRIBUTING.md. Declare them once in [tool.mypy] and reduce those four copies to a bare mypy call. Done when tests/test_guard_wiring.py checks the new form and passes.

由索引模型根据 Issue 内容生成。

描述

area: dev-tooling help wanted severity: low source: roadmap wave: 4

Deferred work · S1-addendum: [tool.mypy] · severity Low · cost ~1 h · recorded in docs/roadmap/risks-and-decisions.md:250

Summary

The typing gate (mypy --strict --follow-imports=silent forgelm/__init__.py forgelm/_version.py tests/typing/public_surface_probe.py) is copied verbatim into ci.yml, CLAUDE.md, AGENTS.md and CONTRIBUTING.md, and only tests/test_guard_wiring.py keeps the copies identical. The Phase 16 S1 addendum deferred a [tool.mypy] single source because it would have changed the gate's invocation in the middle of a review round; that round has closed.

Condition or budget

None left: the reason for deferring (a mid-review change) no longer applies.

State today (re-checked 2026-10-09)

pyproject.toml has no [tool.mypy] section and no mypy.ini exists.

Related

#662 and #686 concern what the gate covers, not where its configuration lives.

Acceptance criteria

  • The flags and files are declared once in [tool.mypy], the four copies become a bare invocation, and tests/test_guard_wiring.py pins the new form.

Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09.

主要语言
Python
星标
9
派生
1
平均合并
8 小时 47 分钟
30 天内合并 PR
47

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

HodeTech/ForgeLM 的其他 Issue

查看 HodeTech/ForgeLM 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。