path: root/.CONTRIBUTING.md.swp

b0VIM 8.1C�i[�ނ6
analinux-bnhr~ana/github/rails/CONTRIBUTING.md
3210#"! Utp
1

ad�
�1����r��G
F
L�"�
�
�	�	�	�	j	i	��('����ut��;:dc$#|{������Rails TeamThanks! :heart: :heart: :heart:Ruby on Rails is a volunteer effort. We encourage you to pitch in and [join the team](http://contributors.rubyonrails.org)!* Please read [Contributing to the Rails Documentation](http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#contributing-to-the-rails-documentation).#### **Do you want to contribute to the Rails documentation?*** 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 have questions about the source 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.* Suggest your change in the [rubyonrails-core mailing list](https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-core) and start writing code.#### **Do you intend to add a new feature or change an existing one?**Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of Rails will generally not be accepted (read more about [our rationales behind this decision](https://github.com/rails/rails/pull/13771#issuecomment-32746700)).#### **Did you fix whitespace, format code, or make a purely cosmetic patch?*** 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.* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.* Open a new GitHub pull request with the patch.#### **Did you write a patch that fixes a bug?*** 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).  * [**Generic template** for other issues](https://github.com/rails/rails/blob/master/guides/bug_report_templates/generic_master.rb)  * [**Action Pack** (controllers, routing) issues](https://github.com/rails/rails/blob/master/guides/bug_report_templates/action_controller_master.rb)  * [**Active Record** (models, database) issues](https://github.com/rails/rails/blob/master/guides/bug_report_templates/active_record_master.rb)* 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**:* 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.* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/rails/rails/issues).  in Rails**, and instead to refer to our [security policy](http://rubyonrails.org/security/).* **Do not open up a GitHub issue if the bug is a security vulnerability#### **Did you find a bug?**## How to contribute to Ruby on Rails