diff options
-rw-r--r-- | guides/source/contributing_to_ruby_on_rails.textile | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/guides/source/contributing_to_ruby_on_rails.textile b/guides/source/contributing_to_ruby_on_rails.textile index eb049aa357..128a968f69 100644 --- a/guides/source/contributing_to_ruby_on_rails.textile +++ b/guides/source/contributing_to_ruby_on_rails.textile @@ -345,6 +345,10 @@ 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: |