You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my network environment, it is very unstable to migrate github repo with https protocol(git clone https://github.com/ownxxx/repoxxx.git), so I have to use ssh protocol(git clone [email protected]:ownxxx/repoxxx.git) to migrate github repo.
when i use the migrate feature of gitea to mirror github repo, and type the ssh url([email protected]:ownxxx/repoxxx.git), it will show the invalid URL message: "is not a valid URL."
does gitea really support migrate github repo with ssh protocol now? or it's my migrate method is wrong?
BTW: i have make and setup the pair of RSA ssh key for github, and can clone the repo successfully with raw command method on the terminal.
thanks a lot!
Screenshots
No response
The text was updated successfully, but these errors were encountered:
hansen6878
changed the title
can't migrate the github repo with ssh protocol
Can't migrate the github repo with ssh protocol
Mar 15, 2022
Gitea Version
1.16.4
Git Version
2.20.1
Operating System
debian10(bluster)
How are you running Gitea?
Database
SQLite
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Description
In my network environment, it is very unstable to migrate github repo with https protocol(git clone https://github.com/ownxxx/repoxxx.git), so I have to use ssh protocol(git clone [email protected]:ownxxx/repoxxx.git) to migrate github repo.
when i use the migrate feature of gitea to mirror github repo, and type the ssh url([email protected]:ownxxx/repoxxx.git), it will show the invalid URL message: "is not a valid URL."
does gitea really support migrate github repo with ssh protocol now? or it's my migrate method is wrong?
BTW: i have make and setup the pair of RSA ssh key for github, and can clone the repo successfully with raw command method on the terminal.
thanks a lot!
Screenshots
No response
The text was updated successfully, but these errors were encountered: