Difference between revisions of "HOW-TO check out PKP applications from git"
m (Protected "HOW-TO check out PKP applications from git" ([edit=sysop] (indefinite) [move=sysop] (indefinite)))
Revision as of 14:14, 22 January 2013
This is the official process to check out OMP with the PKP library as a sub-module. The same process applies to all other PKP projects. Just exchange omp for ojs, ocs or harvester.
Create github.com user
If you want write access to the repository then go to github.com and create your own user account there and log into it. See the github documentation to generate/add your RSA key to your github account.
Delete existing personal forks
First you have to delete existing personal forks of omp/pkp-lib if you have cloned these repositories before. You obviously shouldn't do this when there are still changes in there you don't have in other locations! If you don't have existing forks then you can jump to the next step.
Otherwise do the following:
- Go to your personal github dashboard.
- In "Your Repositories" select the forks you want to delete.
- Go to Admin tab.
- Down on the page click on "Delete This Repository".
- Repeat these steps for both omp and pkp-lib
Fork the official application repositories
- Go to http://github.com/pkp/omp and fork it.
- Go to http://github.com/pkp/pkp-lib and fork it.
- Go to http://github.com/pkp/ojs and fork it.
- Go to http://github.com/pkp/ocs and fork it.
- Go to http://github.com/pkp/harvester and fork it.
You can fork a subset of these projects if you do not intend to work on all of them. You'll always need the pkp-lib repository together with any of the application-specific repositories.
Check out the application(s) on your local machine
Use the shell script checkout.sh to check out each application that you wish to work on:
sh checkout.sh.txt your-user ojs ojs-checkout
In the above example, "your-user" is your github.com username. It will check the "ojs" application out into a directory called "ojs-checkout".
Where to go from here?
Have a look at frequent git use cases for typical git use cases you'll encounter in your day to day work with git.