forge: added support for gitea #610
Conversation
Tested: - [X] Pull request - [X] Create - [X] Assign - [X] Close/Open - [ ] Drafts (no drafts, only WIP prefix) - [X] Milestones - [X] Labels - [X] Assignees - [X] Review-Requests - [-] Issues - [X] Create - [X] Assign - [X] Close/Open - [X] Milestones - [X] Labels - [ ] Marks (there is no such thing in gitea?) - [X] Assignees - [X] Commenting (comment, edit, delete) - [X] Merge
|
This has been suggested a few times before. There also was a pull-request that added notification support (#431). In response to that I started working on that myself. The early results can be seen in the But I abandoned that work. I now think that it was a mistake to support more than one forge initially; it slows down development considerably. The Gitlab implementation, which most other implementations would be based on, is lacking. One problem is callback hell. Until I have improved the Gitlab implementation, I don't want to add other implementations that are based on that. So I'm afraid you will have to maintain that as a separate package and you will also end up having to deal with breaking changes. I'm sorry I cannot do better than that at this time. Forge is a big time sink and I am prioritizing paying of technical dept over supporting more forges (which would mean increasing the dept). |
|
Ok. I will pack it separately. Thank you. |
2 participants
I'm using self hosted gitea on regular basis, so here is the result.
From day to day use I found two bugs:
forge-add-repositorydoesn't pull topics at first time (same behaviour has github)forge-pull-notificationsmost times throw error:Tested:
Any suggestions/tips are welcome.