Zikula Blog

I'd like to explain the process of moving and SVN repo to Github. There are limitations in what you can import because git and subversion are fundamentally different. In most cases it will not affect you, but in some circumstance, it will. I have explained the: potential difficulties here (8 minute video).

Importing projects to github.com is relatively easy but there are some important considerations:

Git branches are contexts, not nodes on a tree, so you cannot not import your whole with from above the trunk, branches and tags folders. If you branched to branches then this has effectively left the trunk from a git perspective. You cannot directly import this. If you must you have to import that branch itself to a separate repo, you can then branch it to a different name and push it back to your main repository. This will create a detached branch with no connection to the trunk - but that's the best you can do. If you have just been tagging from the trunk, you can create branches: just import the trunk, clone down to your local computer, then branch from those points. Tags in SVN are branches. Tags in git are pointers to a commit. You cannot import tags. Tagging must be done after importing. If you have broken by committing code to tags, then again, this has effectively become detached and cannot be tagged.

Recommendations. What is most important is to get your trunk imported and the last maintenance branch. If you have to import a detached branch, it's not the best, but if you first normalise the module structure, then at least context switching will make more sense.

Here is a 14 minute video tutorial if you want to try yourself, otherwise I would be happy to perform the imports for you.

INTEGRATION BETWEEN GITHUB AND THE COZI Github has it's own issue tracker, wiki and downloads system. However, you may chose to keep your cozi project page. The Zikula Core for example has kept the wiki and issue tracker at the core (and disabled them at Github).

It is possible to integrate Github with the Cozi so that commits will appear in your project timeline and ticket will be updated from commit messages. Several steps are required serverside at the Cozi after which you will be asked to configure the Github "Trac service hook" key with an API key (which will be given to you).