mirrors
/
rails
mirror of https://github.com/rails/rails
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
rails/CONTRIBUTING.md

44 lines
2.8 KiB
Markdown
Raw Normal View History

Add specific bug reporting guidelines to contributing.md. [ci skip] Add boldface and bullets to make more readable. Make sentences declarative. Remove "you"s.
2015-12-02 02:02:35 +08:00
## How to contribute to Ruby on Rails
Oops, rdoc -> markdown. This reverts commit 5d95f3209fb2d6155ecd76c7692d0ac71a14726c.
2012-09-18 01:05:43 +08:00
Add specific bug reporting guidelines to contributing.md. [ci skip] Add boldface and bullets to make more readable. Make sentences declarative. Remove "you"s.
2015-12-02 02:02:35 +08:00
#### **Did you find a bug?**
refer to the contributing guide on how to create issues.
2013-03-18 22:12:15 +08:00
Add specific bug reporting guidelines to contributing.md. [ci skip] Add boldface and bullets to make more readable. Make sentences declarative. Remove "you"s.
2015-12-02 02:02:35 +08:00
* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/rails/rails/issues).
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-18 01:15:09 +08:00
Typo in Contributing.md documentation Just fixed a small typo in the documentation.
2016-01-07 07:34:41 +08:00
* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/rails/rails/issues/new). Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.
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 21:38:06 +08:00
Add specific bug reporting guidelines to contributing.md. [ci skip] Add boldface and bullets to make more readable. Make sentences declarative. Remove "you"s.
2015-12-02 02:02:35 +08:00
* If possible, use the relevant bug report templates to create the issue. Simply copy the content of the appropriate template into a .rb file, make the necessary changes to demonstrate the issue, and **paste the content into the issue description**:
* [**Active Record** (models, database) issues](https://github.com/rails/rails/blob/master/guides/bug_report_templates/active_record_master.rb)
* [**Action Pack** (controllers, routing) issues](https://github.com/rails/rails/blob/master/guides/bug_report_templates/action_controller_master.rb)
* [**Generic template** for other issues](https://github.com/rails/rails/blob/master/guides/bug_report_templates/generic_master.rb)
Roll contrib guide link into feature request guidance
2012-09-18 02:29:35 +08:00
Add specific bug reporting guidelines to contributing.md. [ci skip] Add boldface and bullets to make more readable. Make sentences declarative. Remove "you"s.
2015-12-02 02:02:35 +08:00
* For more detailed information on submitting a bug report and creating an issue, visit our [reporting guidelines](http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#reporting-an-issue).
the contributing guide should be mentioned upfront
2012-09-18 22:43:59 +08:00
Add specific bug reporting guidelines to contributing.md. [ci skip] Add boldface and bullets to make more readable. Make sentences declarative. Remove "you"s.
2015-12-02 02:02:35 +08:00
#### **Did you write a patch that fixes a bug?**
* Open a new GitHub pull request with the patch.
* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
* Before submitting, please read the [Contributing to Ruby on Rails](http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html) guide to know more about coding conventions and benchmarks.
#### **Do you intend to add a new feature or change an existing one?**
* Suggest your change in the [rubyonrails-core mailing list](https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-core) and start writing code.
* Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and fixes.
#### **Do you have questions about the source code?**
* Ask any question about how to use Ruby on Rails in the [rubyonrails-talk mailing list](https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-talk).
#### **Do you want to contribute to the Rails documentation?**
* Please read [Contributing to the Rails Documentation](http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#contributing-to-the-rails-documentation).
</br>
Ruby on Rails is a volunteer effort. We encourage you to pitch in and [join the team](http://contributors.rubyonrails.org)!
show love to contributors
2012-09-18 06:32:56 +08:00
Follow-up to #16097 [ci skip] Even if this is not exactly the same, let's add a new-line character instead of two spaces. While it's specified in the Markdown specs that adding spaces at the end of the line creates a break-line tag, this is a brittle approach as people may remove them saving the file on certain editors.
2014-07-18 17:51:36 +08:00
Thanks! :heart: :heart: :heart:
the contributing guide should be mentioned upfront
2012-09-18 22:43:59 +08:00
Rails Team