Add support for using an alternative git hosting platform: forgejo

[yarikoptic]

ATM we rely on github for hosting resultant repositories.

I am seriously considering spinning up an instance of the forgejo-aneksajo:

• RFC: adopting forgejo-aneksajo for DataLad versions of dandisets + issue tracking etc. dandi-utils#14

But I would like not to simply replace all github calls with forgejo ones, but rather make it configurable, so any particular deployment of DANDI infrastructure and this backups2datalad could decide between available choices.

I think overall it would entail the following:

• Investigate if forgejo API endpoints are sufficient to support all implemented here actions against github
• Refactor code to abstract away interaction with remote service endpoints
• Add support for forgejo
• Add functionality to "migrate" from github to forgejo
  • an "alternative" could be to somehow support multiple such remote git backends, might make "migration" to be just a matter of adding one more and eventually removing the "old" one

[jwodder]

@yarikoptic The only GitHub API endpoints that backups2datalad currently uses (though dandi/dandi-infrastructure#64 may add more) are:

• Editing a repository's details — PATCH /repos/{owner}/{name} with a JSON body containing the fields "description", "homepage", and/or "private"
  • Based on https://hub.datalad.org/api/swagger, the equivalent forgejo endpoint supports setting "description" and "private" but not "homepage".
• Creating a release — POST /repos/{owner}/{name}/releases with a JSON body containing the field "tag_name"
  • Based on https://hub.datalad.org/api/swagger, the equivalent forgejo endpoint supports this.

Also, backups2datalad indirectly uses the GitHub API via calls to DataLad's create_sibling_github. Does DataLad have an equivalent method for forgejo?

[yarikoptic]

Also, backups2datalad indirectly uses the GitHub API via calls to DataLad's create_sibling_github. Does DataLad have an equivalent method for forgejo?

not at the moment. I think Michael's group also at time uses/relies on push to create feature of forgejo. But I do not think we should rely on it.