Migrating from OPS4J to GitHub
Qi4j migrated the authoritative repositories from OPS4J's dscm.ops4j.org Gitosis system to GitHub's services around the 1 Nov 2010.
If you don't have a clone from git@dscm.ops4j.org AND have commit rights to a repository there, you can stop reading now. This concerns people who has their repositories cloned from dscm.ops4j.org and either has local commits not yet propagated to the origin, or for some reason don't want to clone again.
Git supports multiple upstream repositories from where you can pull changesets/patches. By utilizing this, we can slowly migrate across, without immediate swap over. By adding the following to each of your repository;
git remote add github git@github.com:Qi4j/<repository>.git
we can continue to pull and push to both the old repository and the new one. Qi4j community members have volunteered to keep the old and the new repositories in sync for a while, probably until ~15th Nov 2010, when the OPS4J repositories will be placed into read-only mode, with a big DEPRECATED notice file showing where to get the latest stuff.
So what does this mean?
If you add the the upstream location, as shown above, you can stop concerning yourself with "origin" and only use github location, such as;
git push github master
git pull github master
If you really want to redirect origin to GitHub, then do the following;
git remote add github git@github.com:Qi4j/<repository>.git
git push github master
git remote rm origin
git remote add origin git@github.com:Qi4j/<repository>.git
git remote rm github
git push github master
git remote rm origin
git remote add origin git@github.com:Qi4j/<repository>.git
git remote rm github
which will first push your local patches to GitHub, then remove the origin before adding a new origin, then removing the temporary github (just in case something goes wrong).
Qi4j and the Qi4j logo are trademarks of Richard Öberg, Niclas Hedhman and the members of the Qi4j Core Team. See Qi4j licensing for more information.
