Support glob/multiple Cobertura files (or action-side merge) in the file input
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
调研方向
该 issue 没有指出任何仓库文件或测试。首先定位必需的 file 输入的实现和上传路径,然后确定 glob、列表或目录输入以及 Cobertura 合并应如何适配;当矩阵和单仓库多项目报告可以在不单独执行合并步骤的情况下上传,或聚合行为已有文档说明时,即可视为完成。
由索引模型根据 Issue 内容生成。
描述
Summary
The file input accepts a single Cobertura XML report. Projects with a test matrix or monorepo layout produce many per-project Cobertura files, so they must be merged into one file before this action can consume them. It would help if the action accepted multiple files / a glob / a directory and merged them itself.
Current behavior
fileis a single, required path to one Cobertura XML report.- There is no glob, multi-file, or directory input.
Desired behavior
Accept any one of:
- glob patterns in
file(e.g.**/*.cobertura.xml), or - a
filesinput taking a newline- or comma-separated list, or - a directory + pattern,
and merge the matched reports (action-side or server-side) before upload. For comparison, codecov/codecov-action accepts multiple files / directory search, so matrix and monorepo setups upload without a separate merge step.
Use case
We're migrating a public .NET OSS monorepo (ChilliCream/graphql-platform) from Codecov to GitHub Code Quality. CI runs a 125-project test matrix, and each job emits its own *.cobertura.xml artifact. Codecov merged them server-side. With this action we now add an explicit merge step first:
- run: dotnet tool install --global dotnet-coverage
- run: >
dotnet-coverage merge
--output merged.cobertura.xml
--output-format cobertura
"**/*.cobertura.xml"
- uses: actions/upload-code-coverage@v1
with:
file: merged.cobertura.xml
language: "C#"
label: code-coverage/dotnet
This works, but native multi-file/glob support (or an action-side merge) would remove the extra tooling and step for the common matrix/monorepo case.
Question
If multiple uploads with distinct labels are made (e.g. one per matrix job), are they aggregated into a single PR coverage total, or treated independently? If aggregation already works that way, documenting it would cover much of this need on its own.
Drafted by Claude (Anthropic AI assistant).
- 主要语言
- Python
- 星标
- 99
- 派生
- 20
- 平均合并
- 12 小时 23 分钟
- 30 天内合并 PR
- 2
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
actions/upload-code-coverage 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
actions/upload-code-coverage#26 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 20/100
-
难度 1/5 1 小时以内 新手友好度 45/100
actions/upload-code-coverage#20 · 2 条评论 · 3 个 reaction ·
-
难度 3/5 1-2 天 新手友好度 58/100
actions/upload-code-coverage#16 · 3 条评论 · 5 个 reaction ·
-
Push to default branch attributes coverage to an unrelated fork PR with a same-named head branch 未关闭
难度 3/5 1-2 天 新手友好度 74/100
actions/upload-code-coverage#14 · 2 条评论 · 1 个 reaction ·
查看 actions/upload-code-coverage 的全部 Issue
相似的 Issue
-
agent-ready documentation needs-triage
难度 1/5 1-3 小时 新手友好度 88/100
-
documentation
难度 1/5 1 小时以内 新手友好度 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" 未关闭
难度 1/5 1 小时以内 新手友好度 92/100
-
instance instance add
难度 1/5 1 小时以内 新手友好度 72/100
searxng/searx-instances#939 · 1 条评论 ·
-
area-deployment area-integrations triage:bot-seen
难度 2/5 半天 新手友好度 86/100