github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-21 14:06:26 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Recursive migration of a repository #14041

New Issue
Closed
opened 2025-11-02 11:01:03 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 11:01:03 -06:00
Owner
Copy Link

Originally created by @CocoXiaoLong on GitHub (Jan 24, 2025).

Feature Description

It would be great for the migrations to support "recursive migrations". As of now, the migrator only clones the repository, but not the submodules. The submodules have to be cloned from the original sources. I think it would be cool to for it to clone those too, while rewriting the .gitmodules to point to the local server.

So in short:

  • migrate repository
  • scan for submodules
  • migrate those too
  • rewrite the .gitmodules

Screenshots

No response

Originally created by @CocoXiaoLong on GitHub (Jan 24, 2025). ### Feature Description It would be great for the migrations to support "recursive migrations". As of now, the migrator only clones the repository, but not the submodules. The submodules have to be cloned from the original sources. I think it would be cool to for it to clone those too, while rewriting the `.gitmodules` to point to the local server. So in short: - [ ] migrate repository - [ ] scan for submodules - [ ] migrate those too - [ ] rewrite the `.gitmodules` ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 11:01:03 -06:00
GiteaMirror commented 2025-11-02 11:01:05 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jan 25, 2025):

It's not easy to do so because the rewriting .gitmodules causes divergence from the origin, it is not a "migration" anymore.

If you have many repositories which need to handle submodules, maybe you need to write your own tool to maintain them, but not letting Gitea to guess how to handle them.

@wxiaoguang commented on GitHub (Jan 25, 2025): It's not easy to do so because the rewriting `.gitmodules` causes divergence from the origin, it is not a "migration" anymore. If you have many repositories which need to handle submodules, maybe you need to write your own tool to maintain them, but not letting Gitea to guess how to handle them.
GiteaMirror commented 2025-11-02 11:01:05 -06:00
Author
Owner
Copy Link

@CocoXiaoLong commented on GitHub (Jan 25, 2025):

That's true. I haven't thought of that. Sorry for taking your time...

@CocoXiaoLong commented on GitHub (Jan 25, 2025): That's true. I haven't thought of that. Sorry for taking your time...
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/proposal
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#14041
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?