Repository navigation
chore(graphify): mark graph.json as generated and undiffable - #1109
Merged
Merged
Conversation
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.
Marks
graphify-out/graph.jsonaslinguist-generated=true -diff.graphify writes
graph.jsonpretty-printed (indent=2, about 1M lines and 40 MB). A refresh diff is too large for GitHub: #1102, #968 and #610 all failed with "diff is taking too long to generate" or showed "0 files changed".Verified: locally,
git diffandgit log -pnow treat the file as binary ("Bin 42 MB → 43 MB" instead of about 1M lines).Not verified: whether GitHub renders a refresh PR once this is on
main. With the attribute only on #1102's branch, the files API still returned 422. This PR merges first so the next refresh can test it. If GitHub still times out, the rule still helps local diffs.