Include TFM in the pre-built report
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- build-system
Research direction
Locate the pre-built report generator and inspect the project.assets.json files used as its input. Trace where projects that bring packages are listed, then include the relevant TFM in that report. Done means source-build reports identify the TFM for each pre-built and make repo-source versus product-build validation easier.
Written by the indexing model from the issue text.
Description
The pre-built report that gets generated as part of the repo source-build would benefit from mentioning the TFM that brings the pre-built in. AFAIK there's a file that mentions the projects that bring the packages in and exactly in there the TFM would be extremely useful to mention.
The scenario here are repos that build both the previous and the current TFM in the repo source-build leg. Those need to understand whether pre-builts only affect the repo-source build or the product build. By mentioning the TFM in the report, that validation would become way easier.
The information is already available in the input source for generating the prebuilt reports, the project.assets.json files.
- Dominant language
- No language data
- Stars
- 287
- Forks
- 146
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 10
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/source-build
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dotnet/source-build#5656 · 2 comments ·
-
area-infra
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dotnet/source-build#5639 · 1 comment ·
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 45/100
dotnet/source-build#5655 ·
-
area-infra
Difficulty 4/5 3-5 days Newbie friendliness 52/100
dotnet/source-build#5636 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
dotnet/source-build#5631 ·
All issues in dotnet/source-build
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oSoWoSo/vOid_Community_repOsitory#147 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
agentic-workflows cascade-suspected
Difficulty 1/5 Under an hour Newbie friendliness 88/100