We have files in our GitHub repo that are technically json files, but don't have a .json extension. when used in the "view" mode in GitHub, the files are treated as plain text, but some of the json files have markdown content inside fields in the json, so the "view" display will display some plain text, some markdown, etc.
like this file: IntuneAuditActivity.workbook
in this case, the autoformatting sees 4 space characters after a couple levels of indentation and thinks this is markdown and shows the rest of the file as code...
is there some way to configure in GitHub how file types are explicitly handled? I can't find it anywhere in the settings.
I was hoping that maybe there was something in .gitattributes for this but nothing jumps out at me so far, and just adding *.workbook text
there didn't seem to have any difference in gihubs' behavior for these files.