Makefile: restrict git diff check
What changed, and why it matters
This is a build-system fix for a flaky CI test. It narrows two 'git diff' checks so they only look at the specific directories they are meant to validate, instead of scanning the entire repository. There is no security issue here.
No security action needed. Treat as a normal CI/build reliability improvement.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies Makefile targets check-doc-examples and check-wire-format. Previously both ran git diff --exit-code HEAD with no path restriction, causing them to fail if any autogenerated file (e.g., gRPC Python protobuf stubs under contrib/pyln-grpc-proto/) changed during the build. The patch restricts the diff to doc and wire respectively, eliminating a race/scope conflict in CI pre-build checks.
Changed components
Makefile targets: check-doc-examples, check-wire-formatInspect captured patch +2 / −2
diff --git a/Makefile b/Makefile
index 079cfa43..85d42d9c 100644
--- a/Makefile
+++ b/Makefile
@@ -663,10 +663,10 @@ update-doc-examples:
TEST_DEBUG=1 VALGRIND=0 GENERATE_EXAMPLES=1 $(PYTEST) $(PYTEST_OPTS) --timeout=1200 tests/autogenerate-rpc-examples.py && $(MAKE) $(MSGGEN_GEN_ALL)
check-doc-examples: update-doc-examples
- git diff --exit-code HEAD
+ git diff --exit-code HEAD -- doc
check-wire-format: extract-bolt-csv
- git diff --exit-code HEAD
+ git diff --exit-code HEAD -- wire
# SECURITY.md and doc/contribute-to-core-lightning/security-policy.md must be
# synced. So far we do this manually.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.