Scala: count the crossScalaVersions a cross-build (sbt +test) runs as toolchains

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python, scala

调研方向

Start by reading the Scala profile and ToolchainAxis.of_job, then trace how job facts are gathered and how toolchains are detected. The issue identifies crossScalaVersions in build.sbt, sbt’s +test task and Mill’s Cross[...] modules as cases to support. Done means cross-build versions are counted as toolchains even when they are declared in build files rather than CI text.

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

描述

Follow-up to #141. The Scala profile counts the Scala versions a job switches to (sbt ++3.3.5 test, scala-cli --scala 3.3.5) as toolchains next to the JDKs. The other common way to test several Scala versions is cross-building: crossScalaVersions := Seq("2.13.16", "3.3.5") in build.sbt and sbt +test in CI, which builds every version in one job. The versions live in the build, not in the CI text, so platform-matrix sees one toolchain (the JDK) for that job.

A ToolchainAxis.of_job only sees the Job; reading crossScalaVersions would need the axis (or the job facts) to combine a build setting with a +-prefixed sbt task. Mill's Cross[...] modules are the same case.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ByTXNqDWdM7HzezrFtEvQt

主要语言
Python
星标
4
派生
1
平均合并
10 小时 41 分钟
30 天内合并 PR
79

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

cpp-best-practices/project_validator 的其他 Issue

查看 cpp-best-practices/project_validator 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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