Comment by hotdogs
If it's JSON it sounds more like config than code. Does it actually need to live in the GitHub repo? Could your application read it from an external location (where ever the rest of your configs live) and reload it on an API call or periodically?
We tried this but the performance hit was too high
* edit: we're building an integration with a SaaS product that doesn't allow us to reference external files due to security, hence having to upload direct to git