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 9b02270ff029499b4ed3da86074472cad2408689
tree 3d3f7df0dd4a9ad74652e63b4b18651a1b43f821
parent 046e32afd3dbae85e1b6dd20efd3bc5090f62f6c
tree 3d3f7df0dd4a9ad74652e63b4b18651a1b43f821
parent 046e32afd3dbae85e1b6dd20efd3bc5090f62f6c
shoulda / CONTRIBUTION_GUIDELINES.rdoc
We’re using GitHub and Lighthouse, and we’ve been getting any combination of github pull requests, Lighthouse 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 a Lighthouse ticket for any submission. If you’ve found a bug and want to fix it, open a new ticket at the same time.
- We’ve got github/lighthouse integration going, so you can update tickets when you commit. This blog post explains the commit options pretty well.
- Please don’t send pull requests Just update the lighthouse ticket 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.







