Skip to content

rust: tools/ci tests get a Cargo.toml so Gazelle generates them (part of #9350, #8597) - #9739

Merged
TrapsterDK merged 1 commit into
mainfrom
rust-gazelle-tools-ci-8597
Nov 9, 2026
Merged

TrapsterDK merged 1 commit into
mainfrom
rust-gazelle-tools-ci-8597

Conversation

@TrapsterDK

Copy link
Copy Markdown
Collaborator

Part of #9350, #8597. Remaining: quality/, cli/entrypoint, cli/lcov, libs/starlark, deploy/, families/generation, rest of tools/ (#9736, #9737, #9738).

Adds tools/ci/Cargo.toml (ci_tests) with a [[test]] for each of the 34 loose test files; Gazelle now generates those 34 rules (names, data, env unchanged). Repinned dx_crates (lock adds only ci_tests). Hand-written # keep markers in tools/ci: 1 before, 1 after (starlark_docs_family_test, reason updated).

Tests: bazel test //tools/ci/...: 34 pass, starlark_docs_test fails (every_rule_aspect_and_attr_has_doc). generate_check reports errors in haskell, javascript/rules and flutter packages, none in tools/ci. No nested-Bazel or consumer tests run.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Xut2hwESun1HL2eSVd1d5B

@TrapsterDK
TrapsterDK force-pushed the rust-gazelle-tools-ci-8597 branch from c8f4de6 to eb7a2e4 Compare November 9, 2026 11:01
@TrapsterDK
TrapsterDK merged commit 7de5aae into main Nov 9, 2026
1 check failed
@TrapsterDK
TrapsterDK deleted the rust-gazelle-tools-ci-8597 branch November 9, 2026 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant