Sung M. Kim** UPDATE: April 21, 2019 **
Both Eugene Karataev & Noah Pederson provided a better way than what's in this post.
Check'em out below.
Instead of creating a new repo, why not just create a fork then set the remote the same way? The git history should be the same, and GitHub will still track it as a forked repository
You git cloned a repository from GitHub without forking it.
The problem is that you made a bunch of changes and want to publish it to a new GitHub repository.
What are the steps required to accomplish it?
TL;DR
Remove original remote and add your own
Scenario
Suppose that you are taking an advantage of all javascript boilerplates floating around on GitHub since setting up Webpack and environment required manually for simple code is a bit too much.
Problem
But when you try to commit the code back to GitHub, you get an error message that you don’t have a permission since the cloned repo belongs to another user.
How to commit to your own GitHub repository
First, remove the remote repository associated using git remote rm origin.
Then create your own repository on GitHub.
After creating the repository, copy the repo URL.
Now, add the URL to your repo.
Now you can push/publish it to your own repository!
Wolla! It’s committed to your GitHub repository.
Alternative
You can simply download a zip version of the repository, git init, then add the remote yourself if you are uncomfortable with git clone.
Resources
Help me improve this~
Git command is very flexible that there might be other ways to do it much easier. Please let me know if there is a way to do it without going through all these troubles 🙂.
The post Push git cloned repository to your own on GitHub appeared first on Slight Edge Coder.
It's not necessary to remove old origin and create a new one. You can just change the existing origin url:
git remote set-url origin NEW_URL