Migrate repositories from a HTTP URL, local disk or SSH URL #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 firstname.lastname@example.org:go-gitea/tea.git --name=gitea/tea
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 gitea does not implement migration from local path
@lafriks I think it does, but is disabled by default.
but from server disk but this would be way to migrate from users local disk
Yes, just like @lafriks said. This in fact will do three steps when migrate from local disk:
- create a repo on gitea server
- git add remote to that gitea server repo
- push to remote server.
The original migration from disk will migrate from gitea server's disk but not guest's.
This command also could be some part of scripts to batch migrate local git repositories to gitea server.
No due date set.
No dependencies set.
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?