dev-to-git | blog post ( markdown file | Blog library
kandi X-RAY | dev-to-git Summary
kandi X-RAY | dev-to-git Summary
is a free and open source blogging platform for developers. dev.to (or just DEV) is a platform where software developers write articles, take part in discussions, and build their professional profiles. We value supportive and constructive dialogue in the pursuit of great code and career growth for all members. The ecosystem spans from beginner to advanced developers, and all are welcome to find their place within our community.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of dev-to-git
dev-to-git Key Features
dev-to-git Examples and Code Snippets
Community Discussions
Trending Discussions on dev-to-git
QUESTION
I was asked to migrate the whole repo on xp-dev and move it to GitHub .
The migration should be smooth, and should contains all the previous commits and history of the xp-dev repo.
I tried to search for a way to do this and found someone asked the same question here, and found this topic on gist.github ,but it didn't help me, as when i tried them i always fail in the last step (push step)
and i got an error says
remote: Repository not found.
fatal: repository https://github.com/userName/repoName not found
I also tried to set the remote repository URL as described in here, but i still got the same error above.
So I was wondering if there's a way to migrate, or what am doing wrong makes me got this error.
...ANSWER
Answered 2020-Aug-10 at 10:03Let's assume we call "old repo" the repository you wish to move, and "new repo" the one you wish to move to.
- Make sure you have a local copy of all "old repo" branches and tags. Fetch all of the remote branches and tags
git fetch origin
- View all "old repo" local and remote branches,
git branch -a
.
If some of the remotes/ branches doesn't have a local copy,checkout to create a local copy of the missing ones, git checkout -b origin/
- Add a "new repo" as a new remote origin,
git remote add new-origin https://github.com/userName/repoName.git
. Now the conf file in .get directory has changed and you can find new-origin added to it. - Push all local branches and tags to a "new repo", (note we're pushing to new-origin),
git push --all new-origin
- Push all tags,
git push --tags new-origin
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install dev-to-git
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page