Skip to content


Subversion checkout URL

You can clone with
Download ZIP
"I’ll do it, but only if you’ll help"
PHP Perl CSS Python JavaScript Shell
Failed to load latest commit information.
bin template_prefix for chivvy emails
commonlib @ 2ec5b5a Update commonlib
conf Ignore files created on deploy.
db Database work for moderation
locale First version of the Portuguese (Portugal) translation, adapted from …
misc Undo damage done by spreadsheet program.
perllib Change final random calls.
phplib Fix front page logic of comment display.
retirement @ f871c26 Remove links to pledge creation/alert, add banner.
templates Fix front page logic of comment display.
web-admin default web-admin page to 'summary'
web Remove links to pledge creation/alert, add banner.
.gitignore Ignore .pyc files (compiled Python)
.gitmodules Remove links to pledge creation/alert, add banner.
LICENSE.txt License file
byarea-todo.txt All the todos and ideas for making geocascading pledges any good in o…



Checking out the code

If you just want read-only access to everything, clone this
repository as with any other, then cd into it and run
    git submodule update --init
to fetch the contents of the commonlib submodule.

If you want to fork your own pledgebank, but don't think
you'll have to alter the common code in commonlib, then
just do the above on your forked version.

If you want to be able to alter commonlib too, then fork
pledgebank and commonlib, and do something like the following
(using dracos' forks as an example here):

$ git clone
$ cd pledgebank/
$ git config submodule.commonlib.url
$ git submodule update --init
Submodule path 'commonlib': checked out 'd49d5b0413b85099397cff550fec7fd94c2943fc'

By specifying a different submodule URL, you've checked out one
that you can push back to. Note that the commonlib will not be
on a branch by default, so you'll have to cd commonlib and
git checkout master (or whatever) to do that.

If you change something in commonlib that you want the parent
project to have, you should first commit/push the change in
commonlib, then git add commonlib and commit from the parent
directory (beware, make sure there's no "/" on the end of
git add otherwise git gets all confused).

You can presumably change from a read-only commonlib to your own
forked version by removing its contents, changing
submodule.commonlib.url, and rerunning git submodule, though
I've never tried that myself.

Something went wrong with that request. Please try again.