If the API base was configurable, this project would theoretically work with most Gitea/Forgejo instances, unless I'm missing a specific workflow unique to Codeberg.
That's a neat idea! I have thought about this for some time aswell already after discovering that codeberg is based on Gitea/Forgejo.
I just have the fear that one day codeberg (or some other instance that I could potentially support) will fork the Gitea/Forgejo project and deviate from their API. Then I would need to maintain multiple APIs or some people would probably get upset. Because of this I decided to tailor the project just for the main codeberg instance.
If you look for similar CLI Apps that support different API bases you can have a look at tea.
If you are really unhappy with all of the things I just said then I still might be convincable for the following: We could, pretty easily, integrate configurable base APIs but then I would add a disclaimer that this is experimental and not maintained for unforeseeable amounts of time.
Hey, just checking back here since I don't know how to interpret your reaction. Do you want to see the changes implemented or can we close the issue?
Ah, my apologies! We can close it, your reasoning makes perfect sense. 🙂
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?