Skip to content

Commit 0a27f8a

Browse files
committed
Remove errant line [ci skip]
1 parent 86fa7a9 commit 0a27f8a

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ issue](https://github.com/rails-api/active_model_serializers/issues/new):
3232
please specify in your report why you can't update to the latest version.
3333
- Operating system type + version.
3434
- Ruby version with patch level. And whether you're using rvm, rbenv, etc.
35-
- Include your ruby -e "puts RUBY_DESCRIPTION".
35+
- Include `ruby -e "puts RUBY_DESCRIPTION"`.
3636
- Clearly-written steps to reproduce the issue (i.e. "Show me how to show myself." ), including:
3737
- What were you doing? Include code if possible.
3838
- Command line parameters used, if any.
@@ -44,7 +44,7 @@ issue](https://github.com/rails-api/active_model_serializers/issues/new):
4444
- The best help here is a failing test. Even better if it's a PR.
4545
- Then the steps to reproduce and/or a gist or repository that demonstrates the defect.
4646
- Then examples of the code you were using.
47-
- Any error messages (including stacktrace, i.e. ""Show me the error.")
47+
- Any error messages (including stacktrace, i.e. "Show me the error.")
4848
- Things you've tried.
4949
- A pull request for your fix would be great. Code should have tests.
5050
- Link to source code, if available.
@@ -54,9 +54,7 @@ If you encounter multiple, unrelated issues, please report them as such.
5454

5555
Simon Tatham has written an excellent on article on
5656
[How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html)
57-
which is well worth reading, although it is not specific to ActiveModelSerializers.
58-
59-
1. What have you tried?
57+
which is [well worth reading](http://yourbugreportneedsmore.info/), although it is not specific to ActiveModelSerializers.
6058

6159
Include as much sample code as you can to help us reproduce the issue. (Inline, repo link, or gist, are fine. A failing test would help the most.)
6260

0 commit comments

Comments
 (0)