C/C++ (CMake + CTest) support: tracking issue

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

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
42/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
c, cmake, cpp, typescript

調査の方向性

Read the adapter guide and the Rust model at src/repo/adapters/rust.ts, then inspect adapter registration in src/repo/adapters/index.ts and the release boundary. The tracking issue lists independent steps; choose an unblocked one and keep unsupported CMake forms in blockers so the full suite runs. Done for a step means its behavior is implemented and covered, with the final replay step requiring a public CMake repository and a published 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. C and C++ are open for contributors and design partners.

First supported setup: a CMake project whose tests are registered with CTest (add_test, or gtest_discover_tests / catch_discover_tests), run with ctest. Selection happens at the CMake target level first.

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

  • Map source files to targets from literal file lists in add_library / add_executable / target_sources
  • Build the target graph from target_link_libraries and add_subdirectory
  • Follow #include "..." to map changed headers to the targets that include them (quoted includes resolved against target_include_directories)
  • Map test targets to CTest tests and generate ctest -R '<regex>' (or ctest -L) commands for the selected tests
  • Fall back with a reason on what the graph can't see: file(GLOB ...), generator expressions, variables built in loops or conditions, include() of custom .cmake modules, configure_file outputs, macro-driven or generated sources, CMakeLists.txt / toolchain / preset changes
  • Register the adapter in REPOSITORY_ADAPTERS (src/repo/adapters/index.ts) and add it to the release boundary
  • Replay on one public CMake repository and publish the report

Ground rules

  • CMake 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".
  • Plain Makefiles, Meson and autotools are out of scope for the first version; they should be detected and fall back to the full suite with a clear reason. Bazel C/C++ is covered by the Bazel tracking issue.
  • Don't run CMake to fill gaps; the engine doesn't install or run project tooling.
  • Read the adapter guide first; the Rust adapter (src/repo/adapters/rust.ts) is a close model for target-level selection.
  • Discuss design questions here, so every step stays consistent.

Using C or C++ 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 を短くまとめたダイジェスト。