Open jpelay opened 2 years ago
I'm sure I've chatted to @danfishgold about this somewhere, but can't find the thread. It's a good future improvements idea.
I'm working on a small tool (the design is in my head) that just calls the same compression method on a file on your local system to get it into the blob format that the app expects after the /file/
path segment -- would that be a viable workaround? It'll be published as a Node script once it exists. It won't do any upload, it'll just output the blob to stdout, so it shouldn't run afoul of any corporate security policies (I'm writing it for the same reason mentioned in the original post -- we did a code reading with some open source code I wrote a while ago, but people want to try it on things in a private repo)
Oh dang, I misinterpreted that parameter, I thought it was a file contents hash, not a hash of the GitHub url. Not a workaround after all 😞
I think this a great tool, and I've found myself wanting to use it on my day to day for understanding code I'm new at, but sometimes this code is not public on github, but rather private on my company's servers. Is it feasible to add an option to upload a file locally and be able to use the code reading tool with those files?