Conversation
A quiet sync is the git-hook path. The stale-index refusal still exits 1, but now writes one line to stderr so a hook that fails the commit on a non-zero exit does not block it for an invisible reason. (colbymchenry#1798)
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An index built with an older extraction version can make
codegraph syncprint “Already up to date” and exit 0 even thoughstatusrecommends a rebuild. With source edits, sync updates only those files and still leaves the index stale.The CLI now checks the existing extraction-staleness signal before incremental work, closes the graph, and exits 1 with a
codegraph indexrecovery instruction.--quietalso exits 1 and prints the reason as a single stderr line, so a git hook that fails on a non-zero exit still shows the user why. Current indexes continue syncing normally; a full index restores successful sync. The guard is confined to the explicit CLI command, preserving library and watcher incremental behavior.Related to #1798: this addresses the misleading CLI success signal, not the proposed automatic background rebuild. It complements #1256's status/upgrade guidance changes.
Validation on Node 24.21.0, Linux/WSL2, based on upstream
3ed73bc:The equivalent fork integration also passed full native (4,742) and WASM (4,740) suites and five deployment probes. Those full-suite results are from the consolidated fork; the focused tests above were rerun on this upstream-only branch. Windows and the viewer build were not rerun for this change.