Skip to content

[ci] disable cpplint header-guard check after repo rename to ExaBoost#11

Merged
BelixRogner merged 1 commit into
masterfrom
fix/cpplint-after-rename
May 10, 2026
Merged

[ci] disable cpplint header-guard check after repo rename to ExaBoost#11
BelixRogner merged 1 commit into
masterfrom
fix/cpplint-after-rename

Conversation

@BelixRogner
Copy link
Copy Markdown
Owner

Why

Cpplint's pre-commit hook uses --root=.. to derive the expected header-guard prefix from the parent directory name. Before the rename that gave LIGHTGBM_INCLUDE_LIGHTGBM_*_H_; after rename to ExaBoost it expects EXABOOST_INCLUDE_LIGHTGBM_*_H_, so every header now fails build/header_guard.

We deliberately did not rename the C/C++ symbols — ExaBoost is binary-compatible with LightGBM (#include <LightGBM/...>, LGBM_* API, import lightgbm). The header guards correctly say LIGHTGBM_*. The lint expectation is what's wrong, not the headers.

Fix

Drop --root=.. and add -build/header_guard to the cpplint filter list, matching what .ci/lint-cpp.sh already does. No code changes; pre-commit config only.

Effect

Resolves the cpplint failure that's currently blocking every PR's Static Analysis check (PRs #4, #6#10 all hit it).

🤖 Generated with Claude Code

cpplint's --root=.. workaround derived the expected header-guard prefix
from the parent directory name. After renaming the repo to ExaBoost,
that prefix changed from LIGHTGBM_INCLUDE_*_H_ to EXABOOST_INCLUDE_*_H_
and every header now fails build/header_guard.

We deliberately did not rename the C/C++ symbols (still LightGBM,
LGBM_*, import lightgbm) to keep ExaBoost binary-compatible. Disable
the header-guard check in the cpplint pre-commit hook to match the
existing setup in .ci/lint-cpp.sh.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@BelixRogner BelixRogner merged commit ed6449f into master May 10, 2026
51 of 52 checks passed
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