Skip to content
nigelmcnie edited this page Feb 26, 2011 · 2 revisions

Ok, this is how plugins work now (using Git Submodules).

Checking out

Previously you'd just do a

git clone https://github.com/ccnz/Ushahidi_Web.git

We still do that, but afterwards we do this:

cd Ushahidi_Web
git submodule init
git submodule update

This will pull all the plugins down as well.

Editing a plugin

Don't edit the submodule directly. It won't work. Instead create a fork of the plugin, then do this

# Enter plugins dir
cd plugins/actionable
# Add a new remote for the plugin from your github fork
git remote add fork git@github.com:redspider/ushahidi-plugins-actionable.git
# Fetch the github fork
git fetch fork
# Check it out and switch into your new feature branch
git checkout -b my_new_feature fork
# Change readme file (it's a feature, honest)
vim README
# Commit with relevant log message
git commit -am "HAHA CHANGES!"
# Switch to master on fork
git checkout master
# Merge your feature
git merge my_new_feature
# Push it back up to your fork
git push fork

Then once you're done and happy, you do a pull request to the main line as usual.

Clone this wiki locally