| Benefit |
|---|
| Dronecode Board of Directors position |
| Technical Steering Committee (TSC) Seat |
| Access to subcommittees |
| Join and create workgroups |
Clang-Tidy is the T2 critical path bottleneck at 11:16 (9:09 is the analysis step, ~1,025 source files, 16 threads). It gates all T3 jobs. A typical PX4 PR touches 1–7 .cpp/.hpp files.
platisd/clang-tidy-pr-comments was evaluated. It consumes a clang-tidy YAML fixes file and posts inline, line-level review comments on the PR diff — including one-click "suggested change" blocks when clang-tidy has a fix. It does not run clang-tidy itself.
This opens a two-layer architecture:
- Gate layer (existing): file-level incremental tidy → CI pass/fail. Catches all issues in changed files.
Date: 2026-02-18
Context: Comparing two independent analyses — one from the repo maintainer (mrpollo) and one from multi-agent research — then synthesizing into a unified implementation plan.
Before diving into differences, the areas of strong convergence are the most important signal:
The current 1,255-line monolithic workflow is a binary proposition for forks: take it all or fork-and-diverge. Every upstream sync creates merge conflicts, every customization requires editing the sacred 1,200-line file, and there is zero out-of-the-box experience.