...
- Create a new repo in Github (or ask for one for the OpenMRS org from code@openmrs.org)
- Name: openmrs-module-yourmoduleid
- Description: a one-line description of what the module does (look at others for examples)
- Make it public
- Initialize with a README
- Add .gitignore for maven
- Edit the module's pom.xml to use the github address
No Format <scm> <connection>scm:git:https://github.com/openmrs/openmrs-module-yourmoduleid/</connection> <developerConnection>scm:git:https://github.com/openmrs/openmrs-module-yourmoduleid/</developerConnection> <url>https://github.com/openmrs/openmrs-module-yourmoduleid/</url> </scm>
- Change the local repo you just converted to point at that one github repo "origin" (below)
Code Block language bash $ git remote add origin https://github.com/openmrs/openmrs-module-yourmoduleid.git
Code Block language bash $ git pull origin master
- Assuming that your module uses the OpenMRS license and it wasn't already in subversion's root, add it:
Code Block language bash wget https://raw.github.com/openmrs/openmrs-core/master/license.txt
- Commit your changes locally
Code Block language bash $ git add . $ git commit -m "migrating from svn to github"
- Push the code to github (below)
Push the tags manually using the following command.Code Block language bash $ git push
Code Block language bash $ git push --tags
- Add default teams to the new github repository:
- Full Committers
- Partial Committers
- Repo Owners
- Under the Admin section for the new github repository, make sure Wiki & Issues are unchecked (we don't want wiki & issues going into github; rather, we want people using wiki.openmrs.org and jira.openmrs.org)
Retiring the SVN project
It's important to clearly indicate to other developers that the SVN project is no longer the active repository for the project. After successfully loading the code into github, rather than delete the project, you should:
...