fix(gitea): use configured endpoint in PR cache

[javiertury]

Changes

Ensure that gitea PR cache uses the endpoint configured by the user

Context

As detailed in issue #32825, renovate paginates using the url returned by gitea, which may change the endpoint. This causes authentication failures since tokens are not attached to the request or a network error if the returned url is not accesible from within the network. Also a gitea instance configured with a http public url would remove transport encryption even if renovate was configured with a https endpoint.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[viceice]

implement RENOVATE_X_REBASE_PAGINATION_LINKS like GitHub

renovate/lib/util/http/github.ts

Line 338 in d0c0aa7

!!process.env.RENOVATE_X_REBASE_PAGINATION_LINKS &&

[javiertury]

What is the advantage of RENOVATE_X_REBASE_PAGINATION_LINKS over the proposed solution? We can address the root of the problem if we eliminate the need to rebase in the first place.

According to gitea docs, the pulls endpoint works with limit-offset pagination and next.url just increases the page counter so both methods are equivalent. It is not the case that next.url uses stateless cursor pagination or something more performant, and even if it was the case my guess is that gitea would provide a well-designed API such that we can pass the cursor through query parameters.

[viceice]

we did the decision some time ago, there where more discussions about it. so please do it like we suggest.

[viceice]

• fix(gitea): Use correct URL in PR Pagination #26876