Skip to content

Latest commit

 

History

History
9 lines (8 loc) · 1.08 KB

CONTRIBUTION_GUIDELINES.rdoc

File metadata and controls

9 lines (8 loc) · 1.08 KB

We’re using GitHub, and we’ve been getting any combination of github pull requests, 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.

  • 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 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.

  • Please don’t submit patches or branches that update the Gem version.