Antonin Delpeuch 55b9aed470 [GITEA] Avoid conflicts of issue and PR numbers in GitLab migration (#1790) ... Closes #1789. The bug was due to the fact that GitLab does not guarantee that issue numbers are created sequentially: some identifiers can be skipped. Therefore, the new pull requests numbers should not be offset by the number of issues, but by the maximum issue number. See for instance https://gitlab.com/troyengel/archbuild/-/issues/?sort=created_date&state=all&first_page_size=20, where there is only a singe issue with number "2". Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/1790 Co-authored-by: Antonin Delpeuch <antonin@delpeuch.eu> Co-committed-by: Antonin Delpeuch <antonin@delpeuch.eu> (cherry picked from commit 2c185c39fe)		2023-12-01 19:17:46 +00:00
..
_api_v4_projects_6590996	[GITEA] Avoid conflicts of issue and PR numbers in GitLab migration (#1790)	2023-12-01 19:17:46 +00:00
_api_v4_projects_6590996_issues?page=1&per_page=10&sort=asc&state=all	[GITEA] Avoid conflicts of issue and PR numbers in GitLab migration (#1790)	2023-12-01 19:17:46 +00:00
_api_v4_projects_6590996_issues_2_award_emoji?page=1&per_page=10	[GITEA] Avoid conflicts of issue and PR numbers in GitLab migration (#1790)	2023-12-01 19:17:46 +00:00
_api_v4_projects_6590996_merge_requests?page=1&per_page=10	[GITEA] Avoid conflicts of issue and PR numbers in GitLab migration (#1790)	2023-12-01 19:17:46 +00:00
_api_v4_projects_6590996_merge_requests_1	[GITEA] Avoid conflicts of issue and PR numbers in GitLab migration (#1790)	2023-12-01 19:17:46 +00:00
_api_v4_projects_6590996_merge_requests_1_award_emoji?page=1&per_page=10	[GITEA] Avoid conflicts of issue and PR numbers in GitLab migration (#1790)	2023-12-01 19:17:46 +00:00
_api_v4_projects_troyengel%2Farchbuild	[GITEA] Avoid conflicts of issue and PR numbers in GitLab migration (#1790)	2023-12-01 19:17:46 +00:00
_api_v4_version	[GITEA] Avoid conflicts of issue and PR numbers in GitLab migration (#1790)	2023-12-01 19:17:46 +00:00