Track TypeScript errors in CI

未关闭
#8,786 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

  • #8787 来自 @talissoncosta —— 已关闭,未合并

评估

难度
4/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions, typescript
领域
ci-cd

调研方向

Start by reading the existing CI workflows to see how lint and unit tests run, and reuse the sticky PR comment already built for Visual Regression. Run tsc --noEmit locally to reproduce the per-file error counts, starting with common/stores/feature-list-store.ts (147 errors). Done when a PR shows the 890 to N comparison against main's merge base and the workflow never blocks a merge.

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

描述

front-end tech-debt

CI runs lint and unit tests but not tsc. Main has about 890 type errors across 351 files, and nothing tells us when a PR adds more.

Add a report on every PR that compares its type errors with main's, without blocking the merge.

  • On push to main: run tsc --noEmit, upload per-file error counts as an artifact
  • On PRs: run tsc once, compare with main's counts for the merge base (fall back to the latest main)
  • Sticky PR comment, like the Visual Regression one:
    • 🟢 "Type errors: 890 → 884 (−6)" when the PR fixes some
    • 🔴 "Type errors: 890 → 892 (+2)", listing the files that gained errors
    • nothing to report when unchanged
  • Not a required check, so it never blocks a merge

Later, once it has proved quiet: consider making it required.

The biggest single file is common/stores/feature-list-store.ts (147 errors), which shrinks with the Flux migration.

主要语言
Python
星标
7.1k
派生
603
平均合并
3 天 8 小时
30 天内合并 PR
102

环境准备

从这里开始

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

Flagsmith/flagsmith 的其他 Issue

查看 Flagsmith/flagsmith 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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