3 ms·
> It’s frustrating that tarball urls are a proprietary thing and not something that was ever standardized in the git protocol. I think there’s a lot of stuff w
by skissane 2y ago
> It’s frustrating that tarball urls are a proprietary thing and not something that was ever standardized in the git protocol.
I think there’s a lot of stuff which is common to the major Git hosters (GitHub, GitLab, etc) - PRs/MRs, issues, status checks, etc - which I wish we had a common interoperable protocol for. Every forge has its own REST API which provides many of the same operations and fields just in an incompatible way. There really should be standardisation in this area but I suppose that isn’t really in the interests of the major incumbents (especially GitHub) since it would reduce the lock-in due to switching costs
- mikepurvis 2y agoYeah, the motivation question is definitely a tricky one. A common REST story also feels like a piece of eventually getting to federated PRs between forges, though it may well be that that's just impossible, particularly given that GitLab has been thinking about it for a decade and hasn't even got a story for federation between instances of itself much less with Github or Bitbucket: https://gitlab.com/gitlab-org/gitlab/-/issues/14116 https://gitlab.com/gitlab-org/gitlab/-/issues/14116