github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Gitlab migration: Migration fails when there are both issues and MRs in the repo #11159

New Issue
Closed
opened 2025-11-02 09:29:21 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 09:29:21 -06:00
Owner
Copy Link

Originally created by @luna-duclos on GitHub (Jul 4, 2023).

Description

When migrating a gitlab repo to gitea, the migration will almost always fail if both MRs and issues are being migrated.
This is because gitlab assigns a seperate number sequence for each of them, so there is an issue 1, an MR 1, issue 2, MR 2, etc.

This doesn't work with gitea, which has a single number sequence for both and doesn't want them to overlap.

I sadly trashed my logs so I do not have them, my apologies :(
I will reproduce it on a test instance if necessary and provide them, please let me know if wanted.

Gitea Version

1.9.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

gitea was being ran using the gitea helm charts found at https://gitea.com/gitea/helm-chart/

Database

PostgreSQL

Originally created by @luna-duclos on GitHub (Jul 4, 2023). ### Description When migrating a gitlab repo to gitea, the migration will almost always fail if both MRs and issues are being migrated. This is because gitlab assigns a seperate number sequence for each of them, so there is an issue 1, an MR 1, issue 2, MR 2, etc. This doesn't work with gitea, which has a single number sequence for both and doesn't want them to overlap. I sadly trashed my logs so I do not have them, my apologies :( I will reproduce it on a test instance if necessary and provide them, please let me know if wanted. ### Gitea Version 1.9.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? gitea was being ran using the gitea helm charts found at https://gitea.com/gitea/helm-chart/ ### Database PostgreSQL
GiteaMirror added the type/bug label 2025-11-02 09:29:21 -06:00
GiteaMirror commented 2025-11-02 09:29:22 -06:00
Author
Owner
Copy Link

@hramrach commented on GitHub (Nov 1, 2023):

This is #13884

@hramrach commented on GitHub (Nov 1, 2023): This is #13884
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11159
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?