Repository navigation
chore: share machine-readable Graphify graph - #290
Merged
Merged
Conversation
A0-42
force-pushed
the
feat/graphify-integration
branch
from
August 31, 2026 14:38
41ddd0d to
307b456
Compare
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
2 participants
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.
Summary
.githooks/pre-commithook runninggraphify update .graphify-out/graph.jsonso agents and contributors share the same graphValidation
sh -n .githooks/pre-commitgraphify update .(incremental local update)git diff --cached --checkThe hook remains opt-in per clone via
git config core.hooksPath .githooks. If generated graph conflicts occur, resolve source-code conflicts first, then regenerategraphify-out/graph.jsonrather than merging the generated JSON manually.