kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

move the info about cosmetic changes to a diff location [ci skip]

Browse source
This commit is contained in:
Vijay Dev 2012-06-14 22:51:29 +05:30
parent 0a83e89222
commit 5795efa9d8
1 changed files with 2 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
guides/source/contributing_to_ruby_on_rails.textile
View file

@ -317,6 +317,8 @@ Now get busy and add or edit code. You’re on your branch now, so you can write
* Include tests that fail without your code, and pass with it.
* Update the (surrounding) documentation, examples elsewhere, and the guides: whatever is affected by your contribution.
TIP: 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.
h4. Follow the Coding Conventions
Rails follows a simple set of coding style conventions.
@ -338,10 +340,6 @@ You should not be the only person who looks at the code before you submit it. Yo
You might want also to check out the "RailsBridge BugMash":http://wiki.railsbridge.org/projects/railsbridge/wiki/BugMash as a way to get involved in a group effort to improve Rails. This can help you get started and help you check your code when you're writing your first patches.
h4. Cosmetic Changes
Changes that are cosmetic in nature and do not improve the stability, functionality, or testability of rails will generally not be accepted.
h4. Commit Your Changes
When you're happy with the code on your computer, you need to commit the changes to git: