.NET (C#) support: tracking issue

未關閉
#137 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
42/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
csharp, typescript
領域
backend, testing

研究方向

Read the adapter guide and use the Maven adapter at src/repo/adapters/maven.ts as the closest model; the registration point is src/repo/adapters/index.ts, and the release boundary is docs/release-boundary.md. Start with one unblocked step, such as mapping SDK-style project files or discovering test projects from a solution. Done means implementing the selected step with conservative blockers for unsupported MSBuild forms; the tracking issue also calls for replaying on a public .NET repository and publishing the report.

由索引模型根據 Issue 內容生成。

描述

adapter enhancement help wanted

DiffCI works out what a change needs from CI, starting with the tests it affects, so AI coding agents (and people) can run them before pushing. It supports JS/TS, Vue, Go, Maven, pytest and Cargo today. .NET (C#) is open for contributors and design partners.

First supported setup: a solution (.sln / .slnx) of SDK-style .csproj projects linked by <ProjectReference>, with test projects using xUnit, NUnit or MSTest, run with dotnet test. Selection happens at the project level first.

Steps (each is one PR; take any that are unblocked):

  • Map files to projects: SDK-style projects include every .cs file under their directory by default, minus nested projects and explicit <Compile Remove> entries
  • Discover test projects (<IsTestProject>, or a reference to Microsoft.NET.Test.Sdk) from the solution file
  • Select test projects by <ProjectReference> dependency, transitively
  • Generate dotnet test path/to/Tests.csproj commands for the selected test projects
  • Fall back with a reason on what the graph can't see: Directory.Build.props / Directory.Build.targets, Directory.Packages.props, global.json, NuGet.config, custom MSBuild targets or imports, conditional ItemGroups, linked files (<Compile Include="../...">), source generators
  • Register the adapter in REPOSITORY_ADAPTERS (src/repo/adapters/index.ts) and add it to the release boundary
  • Replay on one public .NET repository and publish the report

Ground rules

  • MSBuild files are code, not data. Read them statically and only trust simple, recognisable forms; anything else records a blockers entry and DiffCI runs the full suite. An empty graph must never look like "nothing affected".
  • Don't execute dotnet or MSBuild to fill gaps; the engine doesn't install or run project tooling.
  • Read the adapter guide first; the Maven adapter (src/repo/adapters/maven.ts) is the closest model (modules and declared dependencies).
  • Discuss design questions here, so every step stays consistent.

Using .NET and want to help, or have a repository we could test against? Say so below. 👍 this issue if you'd use it; reactions on the language tracking issues decide what comes after.

主要語言
TypeScript
星號
0
分支
4
平均合併
18 小時 41 分鐘
30 天內合併 PR
48

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

DiffCI/core 的其他 Issue

查看 DiffCI/core 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。