Closes #1379 - adds Gitea remote provider#1396
Closes #1379 - adds Gitea remote provider#1396eamodio merged 2 commits intogitkraken:mainfrom septatrix:feature/gitea-provider
Conversation
|
@septatrix This is awesome! Thanks! Yeah, for the icons, its best to keep it b&w. I can't think of anything you've missed or need to consider. Great work! |
|
FYI: I am writing an exam at the end of this week so I will probably not get to adding the icons until next week. |
|
I have now added the icons. As the gitea logo normally has a fully white piece which did not work too well in dark mode with a simple conversion to b/w I borrowed the approach from the |
|
@eamodio How would you like to go forward with this? I am not familiar with the inner workings of this extension so this is probably as far as I am able to implement Gitea support. The best solution would probably be to merge this with the current functionality as most things now work. Support for providers which differentiate between tags and branches can then be tackled in a separate issue. |

Description
Add support for Gitea as a remote (fixes #1379).
Checklist
Fixes $XXX -orCloses #XXX -prefix to auto-close the issue that your PR addressesThe branch parsing logic in particular is a bit different from GitHub and GitLab (shortest branch vs longest branch). This is to match the parsing logic used by gitea for URLs. Also the method to generate URLs from files uses a deprecated route (which is kept for backwards compatibility) as there is no alternative for branchless, SHA-less file paths.
I still need to test the URL parsing for more ambiguous inputs (which even Gitea sometimes handles weird). Also I need to add an icon. Based on the existing icons you prefer black & white variants. Is there anything else I have to watch out for?