Partially Supported Forges ​

B.2.1 Forgejo https://forgejo.org ​

This is the next forge whose API will be supported.

B.2.1.1 Forgejo Hosts ​

B.2.2 Gitea https://gitea.io ​

Once Forgejo is supported it might be fairly simple to support Gitea too, because the former is a fork of the latter, and their APIs might still be similar enough.

B.2.3 Gogs https://gogs.io ​

Once Forgejo is supported it might be fairly simple to support Gogs too, because the Forgejo is a fork of Gitea, which is a fork of Gogs, and their APIs might still be similar enough.

B.2.4 Bitbucket https://bitbucket.org ​

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.

B.2.4.1 Bitbucket Caveats ​

  • The API documentation is poor and initial tests indicated that the implementation is buggy.
  • Atlassian’s offering contains two very distinct implementations that are both called "Bitbucket". Forge only supports the implementation whose only instance is available at https://bitbucket.org, because I only have access to that.
  • Unlike all other forges, Bitbucket does not expose pull-requests as references in the upstream repository. For that reason Forge actually treats it as a semi-forge, not as forge whose API is not supported yet. This means that you cannot checkout pull-requests locally. There is little hope that this will ever get fixed; the respective issue was opened six years ago and there has been no progress since: https://bitbucket.org/site/master/issues/5814.

B.2.4.2 Bitbucket Hosts ​