Support Forgejo as a standalone option (instead of via Gitea)

[filipdutescu]

As a user of Forgejo, I want to be able to use a repository from a forge to be used by Flux. Forgejo is a (now) hard-fork of Gitea which aims to preserve compatibility with it, as much as possible.

Hopefully, this means it should not be too hard to add support for Forgejo and that, at least for the foreseeable future, it should not be too much of a burden, as Gitea is already supported.

[ancashoria]

Did support for Forgejo land in Flux?

[matheuscscp]

Flux works with all Git providers. Support is based on standard protocols: HTTPS and SSH.

This issue is not specific about any particular Git integrations in Flux (e.g. source-controller and image-automation-controller, or notification-controller), so here is the answer for each one:

• For source-controller and image-automation-controller, they work with all Git providers. Support is based on standard protocols: Git over HTTPS and Git over SSH.
• For notification-controller, which integrates with Git provider APIs (not Git protocols), we do support Gitea, and I believe this immediately gives you support for Forgejo. Please test and let us know so we can close this discussion.