This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 78d5e4a8db9d3feebae5f73c024017bb5be866bf
tree 738f7dbe687b9a06681d09ad79fb6a8818b86b2f
parent 39f3e5b6fa82ed803d1e11b1adde26966982a7ca
tree 738f7dbe687b9a06681d09ad79fb6a8818b86b2f
parent 39f3e5b6fa82ed803d1e11b1adde26966982a7ca
shoulda / CONTRIBUTION_GUIDELINES.rdoc
We’re using GitHub, and we’ve been getting any combination of github pull requests, tickets, patches, emails, etc. We need to normalize this workflow to make sure we don’t miss any fixes.
- Make sure you’re accessing the source from the official repository.
- We prefer git branches over patches, but we can take either.
- If you’re using git, please make a branch for each separate contribution. We can cherry pick your commits, but pulling from a branch is easier.
- If you’re submitting patches, please cut each fix or feature into a separate patch.
- There should be an issue for any submission. If you’ve found a bug and want to fix it, open a new ticket at the same time.
- Please don’t send pull requests Just update the issue with the url for your fix (or attach the patch) when it’s ready. The github pull requests pretty much get dropped on the floor until someone with commit rights notices them in the mailbox.
- Contributions without tests won’t be accepted. The file /test/README explains the testing system pretty thoroughly.







