It's hard to know the right approach without knowing more about the projects themselves.
If the projects are intended to be maintained entirely apart from one another after the initial split, as you suggest in your comments, you can simply clone the original project (call it project-a
), change your remote to point to a new repository on GitHub (call it project-b
), and push to that. (This is what your linked article suggests.)
For example:
git clone git@github.com:user/project-a.git project-b
cd project-b
git remote set-url origin git@github.com:user/project-b.git
git remote set-url --push origin git@github.com:user/project-b.git
git push -u origin master
Note that the project-b
repository will need to be created in the GitHub web UI before you can push
.
However, if the projects are closely related it might make sense to use Submodules (or something similar; there are a number of alternatives) to make one a subproject of the other, or to make a common set of libraries a subproject of both of them.