Gitea account integration uses wrong URLs

[mco-dgmr]

I like the Gitea account integration, but I ran into two problems:

1. We are using a locally hosted Gitea instance on a non-standard port number. When using the "Create Pull Request on 'origin'" option, the opened URL does not contain the port number, and so the page doesn’t work.
2. Even if I add the non-standard port number manually, the link doesn’t work, because Gitea also expects the target branch in the compare URL. So Fork currently generates the URL https://scm.example/group/repo/compare/feature%2Fbranch, whereas it should use https://scm.example:5000/group/repo/compare/master...feature%2Fbranch (if the pull request is to be merged into master).

We’re using Gitea 1.16.9, btw.

Originally posted by @mco-dgmr in #1144 (comment)

[TanyaPristupova]

1. We are using a locally hosted Gitea instance on a non-standard port number. When using the "Create Pull Request on 'origin'" option, the opened URL does not contain the port number, and so the page doesn’t work.

I confirm that.

2. Even if I add the non-standard port number manually, the link doesn’t work, because Gitea also expects the target branch in the compare URL.

https://scm.example/group/repo/compare/feature%2Fbranch is legal. This must have been implemented in Gitea 1.16 (go-gitea/gitea#17975) and currently works properly on https://try.gitea.io. For example: https://try.gitea.io/fx6904/gitea/compare/6543-patch-1

[mco-dgmr]

Thank you @TanyaPristupova; I’ll see about upgrading our local version of Gitea to fix the second problem.