forked from thoughtbot/shoulda
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated the contribution guidelines to point to Github Issues instead…
… of Lighthouse
- Loading branch information
Showing
1 changed file
with
4 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,10 @@ | ||
| We're using GitHub[http://github.com/thoughtbot/shoulda/tree/master] and Lighthouse[http://thoughtbot.lighthouseapp.com/projects/5807], 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. | ||
| We're using GitHub[http://github.com/thoughtbot/shoulda/tree/master], 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}[http://github.com/thoughtbot/shoulda/tree/master]. | ||
| * We prefer git branches over patches, but we can take either. | ||
| * 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[http://thoughtbot.lighthouseapp.com/projects/5807] 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}[http://hoth.entp.com/2008/4/11/github-and-lighthouse-sitting-in-a-tree] explains the commit options pretty well. | ||
| * Please <b>don't send pull requests</b> 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. | ||
| * There should be an issue[http://github.com/thoughtbot/shoulda/issues] for any submission. If you've found a bug and want to fix it, open a new ticket at the same time. | ||
| * Please <b>don't send pull requests</b> 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 <tt>/test/README</tt> explains the testing system pretty thoroughly. | ||
|
|
||
|
|