First of all: it's wonderful that you have support for Gogs!
However, nowadays there's a better maintained fork of Gogs called Gitea.
It has nearly 3'000 patches on top of GoGS, more maintainers, more functionality and fixes for bugs that are still present in GoGS (that's the reason why we switched once).
So there are some obvious reasons why someone rather might use Gitea instead of Gogs.
Taiga users might get the impression that Gitea isn't supported though (many won't even know that Gitea is a fork of Gogs). So I guess it would be good to make it clear in the Taiga documentation (and probably in the locales of Taiga).
Hi folks,
First of all: it's wonderful that you have support for Gogs! However, nowadays there's a better maintained fork of Gogs called Gitea. It has nearly 3'000 patches on top of GoGS, more maintainers, more functionality and fixes for bugs that are still present in GoGS (that's the reason why we switched once).
So there are some obvious reasons why someone rather might use Gitea instead of Gogs. Taiga users might get the impression that Gitea isn't supported though (many won't even know that Gitea is a fork of Gogs). So I guess it would be good to make it clear in the Taiga documentation (and probably in the locales of Taiga).
In case you want to make sure that integration works, you can simply test the API integration on the official test instance at
https://try.gitea.io/. There you can also find the Swagger API definition. If you rather want to use a local Gitea instance, you might want to use the official Docker image (there's also an exampledocker-compose.yml).PS: Can you point me to the open Taiga issues for these points please?
Add comments to the connected issues on Taiga when they are created on [Gitea /] Gogs.Create issues on Taiga when they are created on [Gitea /] Gogs.PPS: thank you for your work :pray: