If one does not wish to nuke-and-clone, there is the canonical method:
gosgood@bertha ~/git_repositories/gmic-community/tutorial/Beginner_s_Cookbook $ git remote --verbose
origin https://github.com/grosgood/gmic-community.git (fetch)
origin https://github.com/grosgood/gmic-community.git (push)
upstream https://github.com/dtschump/gmic-community.git (fetch)
upstream https://github.com/dtschump/gmic-community.git (push)
gosgood@bertha ~/git_repositories/gmic-community/tutorial/Beginner_s_Cookbook $ git remote set-url upstream https://github.com/GreycLab/gmic-community
gosgood@bertha ~/git_repositories/gmic-community/tutorial/Beginner_s_Cookbook $ git remote --verbose
origin https://github.com/grosgood/gmic-community.git (fetch)
origin https://github.com/grosgood/gmic-community.git (push)
upstream https://github.com/GreycLab/gmic-community (fetch)
upstream https://github.com/GreycLab/gmic-community (push)
Back at the Beginning of Time, I named the remote reference upstream,
the symbolic name for gmic-community. These commands institute the URL change, formerly at github.com/dtschump
, now at github.com/GreycLab
.
Documentation: Changing a remote repository’s URL
List your remotes first, to be sure you know what your equivalent to my ‘upstream’ label is. Hope this helps.
EDIT: Afterthought — In choosing one or the other approach, the key question is: ‘Do I have local, un-tracked branches with developing content?’ If ‘yes’, then nuke-and-clone will wipe all that. That probably would not make one happy. if you are not sure, then setting the URL is safer. it is non-destructive and reversible - and bandwidth efficient, compare: setting a local string versus a repository download. If one’s workflow is pure ‘pull-commit-push’ on the master
branch, no local branching, git status
reports clean and up-to-date with remotes, and you wish to be done with it, then nuke-and-clone. And you’ve probably done that already anyway.