go-gitea/tea
1
0
Fork 0
mirror of https://github.com/go-gitea/tea.git synced 2026-07-01 21:03:59 -04:00
Code Issues 9 Packages Projects Releases Wiki Activity

[GH-ISSUE #22] Migrate repositories from a HTTP URL, local disk or SSH URL #10

New Issue
Open
opened 2026-02-16 12:57:47 -05:00 by yindo · 6 comments
yindo commented 2026-02-16 12:57:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @lunny on GitHub (Apr 26, 2019).
Original GitHub issue: https://github.com/go-gitea/tea/issues/22

If we can implement a sub command migrate, that will be helpful.

# migrate from a http URL
tea --login=try migrate https://github.com/go-gitea/tea.git --name=gitea/tea

# migrate from local disk
tea --login=try migrate ./tea.git --name=gitea/tea

# migrate from a SSH URL, clone from ssh and then upload from local disk
tea --login=try migrate git@github.com:go-gitea/tea.git --name=gitea/tea
Originally created by @lunny on GitHub (Apr 26, 2019). Original GitHub issue: https://github.com/go-gitea/tea/issues/22 If we can implement a sub command `migrate`, that will be helpful. ``` # migrate from a http URL tea --login=try migrate https://github.com/go-gitea/tea.git --name=gitea/tea # migrate from local disk tea --login=try migrate ./tea.git --name=gitea/tea # migrate from a SSH URL, clone from ssh and then upload from local disk tea --login=try migrate git@github.com:go-gitea/tea.git --name=gitea/tea ```
yindo added the enhancement label 2026-02-16 12:57:47 -05:00
yindo commented 2026-02-16 12:57:48 -05:00
Author
Owner
Copy Link
Copy Source

@noerw commented on GitHub (Apr 26, 2019):

I'm not well informed about the architecture, but afaik the gitea server implements migration logic for all these cases..
If so, the CLI shouldn't need to push from local disk, but trigger the migration on server side for the HTTP/SSH URL case.
This way the local clone can be made optional (with a --clone BooleanFlag?), which might be of interest for large automated migrations.

@noerw commented on GitHub (Apr 26, 2019): I'm not well informed about the architecture, but afaik the gitea server implements migration logic for all these cases.. If so, the CLI shouldn't need to push from local disk, but trigger the migration on server side for the HTTP/SSH URL case. This way the local clone can be made optional (with a `--clone` BooleanFlag?), which might be of interest for large automated migrations.
yindo commented 2026-02-16 12:57:48 -05:00
Author
Owner
Copy Link
Copy Source

@lafriks commented on GitHub (Apr 26, 2019):

@noerw gitea does not implement migration from local path

@lafriks commented on GitHub (Apr 26, 2019): @noerw gitea does not implement migration from local path
yindo commented 2026-02-16 12:57:48 -05:00
Author
Owner
Copy Link
Copy Source

@techknowlogick commented on GitHub (Apr 26, 2019):

@lafriks I think it does, but is disabled by default.

@techknowlogick commented on GitHub (Apr 26, 2019): @lafriks I think it does, but is disabled by default.
yindo commented 2026-02-16 12:57:48 -05:00
Author
Owner
Copy Link
Copy Source

@lafriks commented on GitHub (Apr 26, 2019):

but from server disk but this would be way to migrate from users local disk

@lafriks commented on GitHub (Apr 26, 2019): but from server disk but this would be way to migrate from users local disk
yindo commented 2026-02-16 12:57:48 -05:00
Author
Owner
Copy Link
Copy Source

@lunny commented on GitHub (Apr 26, 2019):

Yes, just like @lafriks said. This in fact will do three steps when migrate from local disk:

  1. create a repo on gitea server
  2. git add remote to that gitea server repo
  3. push to remote server.

The original migration from disk will migrate from gitea server's disk but not guest's.

@lunny commented on GitHub (Apr 26, 2019): Yes, just like @lafriks said. This in fact will do three steps when migrate from local disk: 1. create a repo on gitea server 2. git add remote to that gitea server repo 3. push to remote server. The original migration from disk will migrate from gitea server's disk but not guest's.
yindo commented 2026-02-16 12:57:48 -05:00
Author
Owner
Copy Link
Copy Source

@lunny commented on GitHub (Apr 26, 2019):

This command also could be some part of scripts to batch migrate local git repositories to gitea server.

@lunny commented on GitHub (Apr 26, 2019): This command also could be some part of scripts to batch migrate local git repositories to gitea server.
yindo changed title from Migrate repositories from a HTTP URL, local disk or SSH URL to [GH-ISSUE #22] Migrate repositories from a HTTP URL, local disk or SSH URL 2026-06-05 16:34:07 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
kind/build
pull-request
Mirrored from GitHub Pull Request
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: go-gitea/tea#10
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?