unfortunately the git feature for getting the contents of specific files `git archive` is off by default so it makes getting the README.md challenging. many git server implementations expose raw files in a repo over https using similar APIs. Unfortunately some of them don't allow display directly CORS and other eg github have heavy throttling. until last week I was proxying requests to allow support for git servers without CORs exceptions but I have, perhaps temporarily turned that off so gitworkshop.dev could be entirely statically built. when I wrote the feature it supported (with the proxy): self-hosted: gitea, forgejo and gitlab hosted: github, bitbucket.org, gitlab.org, gitea.com, codeberg.org, sourcehut, launchpad.net feedback welcome on how to proceed with this. I'm thinking about opening a PR for @fiatjaf's song to expose the raw files over https. would you be interested in this @fiatjaf?

Replies (1)

Instead of running to try to catch up with a bunch of proprietary git servers we should have a standard first, then I would gladly accept it or implement it myself on song. That native git feature you mentioned would be my first candidate for such a standard, but last time I tried to implement it on song I failed.