You can try it, change the remote address from gitlab to your original github address, then create a new branch, push to the new remote branch, then clone the remote repo, and merge the newly created branch on the master.
Also, since you migrated from github before, the earliest commit records are actually there. There is really no need to migrate back to the old repo on github. It is easier to create a new repo.
Create a repo on Github, then go to your repo, modify the remote url, and then
You can try it, change the remote address from gitlab to your original github address, then create a new branch, push to the new remote branch, then clone the remote repo, and merge the newly created branch on the master.
Also, since you migrated from github before, the earliest commit records are actually there. There is really no need to migrate back to the old repo on github. It is easier to create a new repo.
If it’s a previous repo, then theoretically
git push [repo url]
应该是可行的,不过对于有可能出现的冲突,还是直接--force
. That solves the problem, right?In addition, I would like to use a space to discuss with the subject, what aspects of Gitlab do not meet the needs of your team?