aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorJonathan Roes <jroes@jroes.net>2013-03-05 00:15:07 -0500
committerJonathan Roes <jroes@jroes.net>2013-03-05 00:15:07 -0500
commit55269f9849154b20cfb927cb8db246c1b2270207 (patch)
treec7f44d1cfdd1504fb0112d8a730a532ee3eda9ba /guides
parent0c3998782b455c81a0cb857a7bd4c90c5ab2e821 (diff)
downloadrails-55269f9849154b20cfb927cb8db246c1b2270207.tar.gz
rails-55269f9849154b20cfb927cb8db246c1b2270207.tar.bz2
rails-55269f9849154b20cfb927cb8db246c1b2270207.zip
Remove reference to BugMash. Link hasn't been updated in 4 years.
Diffstat (limited to 'guides')
-rw-r--r--guides/source/contributing_to_ruby_on_rails.md2
1 files changed, 0 insertions, 2 deletions
diff --git a/guides/source/contributing_to_ruby_on_rails.md b/guides/source/contributing_to_ruby_on_rails.md
index 7909a00c47..cc4e369e7d 100644
--- a/guides/source/contributing_to_ruby_on_rails.md
+++ b/guides/source/contributing_to_ruby_on_rails.md
@@ -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 you’re 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 can’t convince one other developer of the beauty of your code, you’re 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: