I thought it was a neat article, I assumed it was talking about git lfs.

It would be neat if github could store all its data in git, similar to fossil scm. But I suppose microsoft would not want to lose lockin.

"It would be neat if github could store all its data in git, similar to fossil scm."

Yes, that would be very nice - it is unfortunate that you have to make API calls (over http) to get things like issues ...

I think you can get the wiki with plain old 'git' ? I forget ...

> I think you can get the wiki with plain old 'git' ? I forget ...

This is correct. The wiki for a repo is accessible as a separate repository named with a suffix of “.wiki”.

So if user foo has a repo bar with an associated wiki, and the repo URL is https://github.com/foo/bar then you can clone the repo and the wiki respectively over SSH by:

    git clone [email protected]:foo/bar.git

    git clone [email protected]:foo/bar.wiki.git

I believe this is true of gitlab and other providers as well, correct ?

That is, you need API calls to get things like issues.

Is there a single tool that will handle downloading (and the associated API calls) from all of the major providers ? Or is each API tool specifically for either github or gitlab or sr.ht or whatever ?

Every issue system has its own API and today there's no standard for interchange. It would be interesting to see an attempt to try to build a reusable standard, but I don't know what sort of standards agency exists with the guts to try something like, I don't envy the political battle that would entail, and having seen some of the horrors of bespoke Jira and TFS configurations I'm mostly such a standard would either be too minimalist and disappoint too many people or too maximalist and impossible to build.

Yes, I understand each providers standard is different - and I agree that would be a real mess to wrangle.

What I am wondering is are there any tools that use these APIs that have built-in support for multiple provider APIs ? Or does every tool that (helps you manage or download issues, etc.) just built for a particular provider ?

Thanks.

Most of the other such tools I've seen barely have the resources to import/export a single such API. git-issue only has Github import it looks like. https://github.com/dspinellis/git-issue

There's perceval which is designed to be a generic archival tool and supports lots of APIs, but only dumps them to source-specific formats and would still need a lot of work if you tried to use issues from different APIs together: https://github.com/chaoss/grimoirelab-perceval