Antonin Delpeuch 51fab30187 [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) (cherry picked from commit 8f68dc4c9c) (cherry picked from commit 7e932b7fca) (cherry picked from commit 6bbe75ecf8) (cherry picked from commit b18c2e8d65) Conflicts: services/migrations/gitlab.go https://codeberg.org/forgejo/forgejo/pulls/2075 (cherry picked from commit abc129c762) (cherry picked from commit 28884fac10) (cherry picked from commit 5f528dd85f) (cherry picked from commit cb9b8a31b2) (cherry picked from commit 97f02df163) (cherry picked from commit 4611e10e6a)		2024-02-05 16:09:41 +01:00
..
full_download
skipped_issue_number	[GITEA] Avoid conflicts of issue and PR numbers in GitLab migration (#1790)	2024-02-05 16:09:41 +01:00