What is Sahana?
Why we moved to GitHub?
Migrating existing Branches from Launchpad
Therefore, I have already moved them to GitHub as separate branches under my fork of sahana/vesuvius in here. If your individual branch is not listed here (don’t get mad at us!), please read this guideline to migrate that to GitHub. But please make sure that your commit history is entirely kept with valid email addresses attached. One of the big issues that we ran into was that some commits were not linked with valid email addresses.
- This will list down all commits that are not associated with a valid email address.
$ git shortlog -es|sort -rn |grep -Ev "@.+\."
If your branch is listed above and you want to quickly get on with continuing your development work on GitHub, following is a brief guideline.
- Go to https://github.com/sahana/vesuvius and fork the Sahana Vesuvius project.
- Get a local copy of the forked repository.
$ git clone firstname.lastname@example.org:<your_name>/vesuvius
- Move into local repository directory
$ cd vesuvius
- Import your branches to local repository. This will import <export_branch_name> as <branch_name> in your repository. Repeat this for each branch that you wish to import.
$ git fetch http://github.com/ravihansa3000/vesuvius <export_branch_name>:<branch_name>
- Push all your local branches to your GitHub fork.
$ git push -a origin
- Now you can work on any of those branches by doing:
$ git checkout <branch_name>
- And later pushing back to GitHub by:
$ git push origin <branch_name>
- You can add official Sahana Vesuvius master branch as a remote tracking branch
$ git remote add --track master vesuvius git://github.com/sahana/vesuvius
- To get new updates:
$ git fetch vesuvius
- To merge it into your own project:
$ git merge vesuvius/master
- Many thanks to Chamindra de Silva and Usman Akeju for their help.
- Huge shout out to Ramindu Deshapriya for making this task possible!