Redirecting git/github project to fork?

If the official ‘main’ repo of a git project, either in general or in GitHub, has been moved to a new location or to one of its forks, is there a convention, that can be used indicate the new ‘main’ repo?

I had been thinking of adding a file ‘MOVED’, with the new URL as text, but if there is already a convention, then I would rather use that. Optionally, does npm recognize any conventions for this?

  • Bower refuses to install from github fork
  • What are the differences between .gitignore and .gitkeep?
  • Public and private code in a single Git repository
  • How Do I Push an Existing Eclipse Project Up to Bitbucket With EGIT?
  • Is there a git rev spec that specifies the staged file(s)?
  • Unable to perform git-svn clone on a sub-repository requiring AD authentication
  • Automatically abort a “failed” git rebase?
  • Git merge – Access to: theirs; ours; merged-with-conflicts & nearest-ancestor
  • Open two GIT branches in two separate IDE instances?
  • Use git svn to roll back some changes on the svn server?
  • Using maven-release-plugin to tag and commit to non-origin
  • How can I remove my last commit in my local git repository
  • One Solution collect form web for “Redirecting git/github project to fork?”

    There’s no real “hard” convention that I know of. On GitHub, most people seem to:

    • transfer the repo to its new owner
    • ensure that your copy appears as a fork of the “new” repository (possibly by removing it and then forking it from its new location)
    • put a message in the README and in the repo description about its new location.

    This is for example what happened with OfflineIMAP: old location, new location.

    However I doubt that npm recognizes this. You’ll probably have to update the repository URL there.

    Git Baby is a git and github fan, let's start git clone.