All I wanted was that people could use self-hosted or niche git servers without having to feel like they were leaving a lot behind on GitHub, but now you're making GitHub the standard again.
Not a big deal, but meh.
Why is git clone inefficient?
Login to reply
Replies (2)
Yeah it leave a bad taste in my mouth too. I'm not sure its a good idea to have a better experience for people who are using github as the git server. Its contrary to the philosophy of the project. Maybe I should just pull the feature until it can be supported no matter the git server.
why is git clone inefficent? to display a readme we need to download potentially thousands of commits and (I think) all the files present in the tip of the master branch. with `git archive --remote <url>` we just download a tar compressed readme.
I now have this working for self-hosted gitea, forgejo and gitlab instances. Also for many hosted solutions eg bitbucket.org, sourcehut and lauchpad.net. It turns out that a lot of services redirect https://domain/repo/raw/HEAD/README.md to the raw file with CORS enabled.