diff options
author | Prathamesh Sonpatki <csonpatki@gmail.com> | 2015-01-14 16:37:36 +0530 |
---|---|---|
committer | Prathamesh Sonpatki <csonpatki@gmail.com> | 2015-01-14 16:37:36 +0530 |
commit | bd13ff68ef46ae4389c7afd7a9450e7422813948 (patch) | |
tree | 5408db90a8d92c18a7036e56e364a796c1758d2d /guides | |
parent | 7ba24831d7f809d54e88607db8f7d21780efbdfb (diff) | |
download | rails-bd13ff68ef46ae4389c7afd7a9450e7422813948.tar.gz rails-bd13ff68ef46ae4389c7afd7a9450e7422813948.tar.bz2 rails-bd13ff68ef46ae4389c7afd7a9450e7422813948.zip |
Changed "in GitHub" to "on GitHub" [ci skip]
- Followup of https://github.com/rails/rails/pull/18503.
Diffstat (limited to 'guides')
-rw-r--r-- | guides/source/contributing_to_ruby_on_rails.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/contributing_to_ruby_on_rails.md b/guides/source/contributing_to_ruby_on_rails.md index 84e6627c3a..7381521658 100644 --- a/guides/source/contributing_to_ruby_on_rails.md +++ b/guides/source/contributing_to_ruby_on_rails.md @@ -26,7 +26,7 @@ NOTE: Bugs in the most recent released version of Ruby on Rails are likely to ge ### Creating a Bug Report -If you've found a problem in Ruby on Rails which is not a security risk, do a search in GitHub under [Issues](https://github.com/rails/rails/issues) in case it has already been reported. If you are unable to find any open GitHub issues addressing the problem you found, your next step will be to [open a new one](https://github.com/rails/rails/issues/new). (See the next section for reporting security issues.) +If you've found a problem in Ruby on Rails which is not a security risk, do a search on GitHub under [Issues](https://github.com/rails/rails/issues) in case it has already been reported. If you are unable to find any open GitHub issues addressing the problem you found, your next step will be to [open a new one](https://github.com/rails/rails/issues/new). (See the next section for reporting security issues.) Your issue report should contain a title and a clear description of the issue at the bare minimum. You should include as much relevant information as possible and should at least post a code sample that demonstrates the issue. It would be even better if you could include a unit test that shows how the expected behavior is not occurring. Your goal should be to make it easy for yourself - and others - to replicate the bug and figure out a fix. |