Update Git Attributes for JSON syntax highlighting in *.graphite
files
#1752
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.
This is just the type of small PR that I always compulsively do when I encounter a project with a new filetype 馃槅
This will apply the JSON syntax highlighting to some
*.graphite
files on GitHub (syntax highlighting is disabled for large minified files). It marks most*.graphite
files as binary and generated, hiding diffs locally and in GitHub PRs. It reverts this for the graphite test files, since they seem to be manually written.Currently, whether or not syntax highlighting is applied to
test_files/*.graphite
seems to almost be random (linguist's Bayesian classifer timing out perhaps 馃し), but you can see in my fork that syntax highlighting is always applied.