Support Forgejo #1325
Description
Activity
@JCHacking, Have you tried just setting the semantic_release.remote.type = "gitea" and then provided additional configuration such as the domain name and other settings for your environment. I don't have a forgejo environment to test in so I would appreciate you trying it first.
Hi @codejedi365
You can use the forgejo test environment
https://v12.next.forgejo.org/I think it would be the easiest way to test everything well.
I still don't have a Forgejo environment available for testing, as it is still being set up in my company.
@JCHacking, thanks. I'll have to check it out. You will likely get an opportunity to test it before I do so let me know if it ends up working.
Reacted by Juan CruzIt has been 90 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
No update, still in backlog
It has been 90 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Here is my first attempt to add Forgejo support https://github.com/keestux/python-semantic-release/tree/feat/add-forgejo-support
At the moment it is totally untested. I need to figure out how. Meanwhile I'm also learning how I can use python-semantic-release in my project.
@codejedi365 or @JCHacking How do I pass a gitea_token to the release action?
Or, do you perhaps know of an example where python-sematic-release is used in a Gitea action?
Or, is there a forum somewhere to discuss about python-sematic-release?
It has been 90 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Feature Request
Description
Add support for Forgejo
Use cases
People who have repositories in forgejo will be able to use this tool completely.
Possible implementation
Add the implementation of Forgejo as an HVCS, it is very likely to be the same as Gitea since it is a fork of it (although there could be differences, since a fork does not have to be exactly the same).
Alternative solutions
Forgejo could be aliased to Gitea (as long as it is 100% compatible).
Although this does not seem to me the best option because it may eventually cease to be so.