Currently Forge supports two forges and three more forges partially. Additionally it supports four semi-forges. Support for more forges and semi-forges can and will be added.
Both forges and semi-forges provide web interfaces for Git repositories. Forges additionally support pull-requests and issues and make those and other information available using an API.
When a forge is only partially supported, then that means that only the functionality that does not require the API is implemented, or in other words, that the forge is only supported as a semi-forge.
A host is a particular instance of a forge. For example the hosts
https://gitlab.com and https://salsa.debian.org are both instances of
the Gitlab forge. Forge supports some well known hosts out of the box
and additional hosts can easily be supported by adding entries to the
For more details about the caveats mentioned below (and some others) also see Getting Started.
Forge’s support for Github can be considered the "reference implementation". Support for other forges can lag behind a bit.
updated_atfield being updated when appropriate. For Github pull-requests at least, that is not always done.
This is the next forge whose API will to be supported.
forge-alistbecause I couldn’t find any other more trustworthy and persistent public instances but needed something for testing purposes. The Gitea maintainers plan to create their own instance, see https://github.com/go-gitea/gitea/issues/1029. Once that is available, I will probably remove teahub.io again.
Once Gitea is supported it should be fairly simple to support Gogs too, because the former is a fork of the latter and the APIs seem to still be very similar.
I don’t plan to support Bitbucket’s API any time soon, and it gets less likely that I will every do it every time I look at it.