14 commits

Author	SHA1	Message	Date
Nishant Modak	da5ac71885	correct markdown usage [ci skip]	2014-07-09 01:32:44 +05:30
Jeremy Walker	19f9416c38	Add info about contributing to docs to CONTRIBUTING.md ... Encourage more people to contribute to Rails docs by mentioning it in the contribution guide.	2013-06-06 17:57:13 +01:00
Yves Senn	09fced4ec5	refer to the contributing guide on how to create issues.	2013-03-18 15:13:37 +01:00
Xavier Noria	ade701045f	add some kindness	2012-09-18 17:57:37 +02:00
schneems	e69476a5b6	Stronger wording in Contributing file ... Explicitly tell users to read the guide before submitting code. re: #7677. Specify the name of the mailing list for rubyonrails-talk to help differentiate it from rubyonrails-core mailing list.	2012-09-18 08:51:26 -07:00
Xavier Noria	bfcbaa5547	the contributing guide should be mentioned upfront	2012-09-18 16:43:59 +02:00
Francesco Rodríguez	eeb9635ffa	show love to contributors	2012-09-17 17:32:56 -05:00
Jeremy Kemper	a95ddf6475	Roll contrib guide link into feature request guidance	2012-09-17 11:29:35 -07:00
Xavier Noria	84a1e408d7	removes spurious quote	2012-09-17 20:15:27 +02:00
Xavier Noria	4714c8abdc	edits a little bit CONTRIBUTING.md [ci skip]	2012-09-17 20:13:25 +02:00
Steve Klabnik	56071b37d0	Improve CONTRIBUTING.md ... Noting that we don't take feature requests or 'help me' stuff on the Issues tracker should cut down a ton on bad Issues.	2012-09-17 20:23:15 +03:00
Jeremy Kemper	40eec14cea	Oops, rdoc -> markdown. ... This reverts commit 5d95f3209f.	2012-09-17 10:07:13 -07:00
Jeremy Kemper	5d95f3209f	GitHub isn't rendering Markdown for CONTRIBUTING.md. Rely on autolinked URL instead.	2012-09-17 10:04:36 -07:00
Jeremy Kemper	1d6668dec0	Point to the contributing-to-Rails guide	2012-09-17 10:01:05 -07:00