C/C++ (CMake + CTest) support: tracking issue
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 42/100
- Tipo de issue
- Funcionalidade
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- c, cmake, cpp, typescript
- Domínio
- build-system, devtools, testing-qa
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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_librariesandadd_subdirectory - Follow
#include "..."to map changed headers to the targets that include them (quoted includes resolved againsttarget_include_directories) - Map test targets to CTest tests and generate
ctest -R '<regex>'(orctest -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.cmakemodules,configure_fileoutputs, 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
blockersentry 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.
- Linguagem predominante
- TypeScript
- Estrelas
- 0
- Forks
- 4
- Merge médio
- 18h 41min
- PRs com merge (30d)
- 48
Preparar o ambiente
Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de DiffCI/core
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 1 dia
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at randomTalvez já em andamento @FredApps assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 86/100
Mantenedores costumam responder em até 1 dia
-
Agent tools: changed_files lists only the new path of a renamed fileTalvez já em andamento @FredApps assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
DiffCI/core#243 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
adapter good first issue
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
Mantenedores costumam responder em até 1 dia
Todas as issues de DiffCI/core
Issues semelhantes
-
agent-ready area: ui-server priority: p3 type: test
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
schlessera/brain-kit#4249 ·
Mantenedores costumam responder em até 1 dia
-
documentation tool triaged
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 73/100
can1357/oh-my-pi#19608 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
dependencies tech-debt
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
bcgov/nr-waste-plus#1549 ·
Mantenedores costumam responder em até 1 dia
-
enhancement good first issue
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
blixvip/solana-tx-parse#18 ·