.NET (C#) support: tracking issue

オープン
#137 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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分
マージ済み PR(30日)
48

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

DiffCI/core のほかの issue

DiffCI/core の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。