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

Remove reference to BugMash. Link hasn't been updated in 4 years.

This commit is contained in:
Jonathan Roes 2013-03-05 00:15:07 -05:00
parent 0c3998782b
commit 55269f9849

View file

@ -250,8 +250,6 @@ Your name can be added directly after the last word if you don't provide any cod
You should not be the only person who looks at the code before you submit it. You know at least one other Rails developer, right? Show them what youre doing and ask for feedback. Doing this in private before you push a patch out publicly is the “smoke test” for a patch: if you cant convince one other developer of the beauty of your code, youre unlikely to convince the core team either.
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.
### Commit Your Changes
When you're happy with the code on your computer, you need to commit the changes to Git: