Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

GitHub removed voting on issues a while ago [ci skip]

  • Loading branch information...
commit 1d4ae9ff473fc956f5ea7eabda1330110b2cfbc5 1 parent 5906ea9
@sferik sferik authored
Showing with 16 additions and 10 deletions.
  1. +16 −10 README.md
View
26 README.md
@@ -97,29 +97,35 @@ Here are some ways *you* can contribute:
* by suggesting new features
* by writing or editing documentation
* by writing specifications
-* by writing code (**no patch is too small**: fix typos, add comments, clean up inconsistent whitespace)
+* by writing code (**no patch is too small**: fix typos, add comments, clean up
+ inconsistent whitespace)
* by refactoring code
* by closing [issues](https://github.com/rubygems/gems/issues)
* by reviewing patches
## Submitting an Issue
-We use the [GitHub issue tracker](https://github.com/rubygems/gems/issues) to track bugs and
-features. Before submitting a bug report or feature request, check to make sure it hasn't already
-been submitted. You can indicate support for an existing issue by voting it up. When submitting a
-bug report, please include a [Gist](https://gist.github.com/) that includes a stack trace and any
-details that may be necessary to reproduce the bug, including your gem version, Ruby version, and
-operating system. Ideally, a bug report should include a pull request with failing specs.
+We use the [GitHub issue tracker](https://github.com/rubygems/gems/issues) to
+track bugs and features. Before submitting a bug report or feature request,
+check to make sure it hasn't already been submitted. When submitting a bug
+report, please include a [Gist](https://gist.github.com/) that includes a stack
+trace and any details that may be necessary to reproduce the bug, including
+your gem version, Ruby version, and operating system. Ideally, a bug report
+should include a pull request with failing specs.
## Submitting a Pull Request
1. Fork the project.
2. Create a topic branch.
3. Implement your feature or bug fix.
4. Add documentation for your feature or bug fix.
-5. Run <tt>bundle exec rake doc:yard</tt>. If your changes are not 100% documented, go back to step 4.
+5. Run <tt>bundle exec rake doc:yard</tt>. If your changes are not 100%
+ documented, go back to step 4.
6. Add specs for your feature or bug fix.
-7. Run <tt>bundle exec rake spec</tt>. If your changes are not 100% covered, go back to step 6.
+7. Run <tt>bundle exec rake spec</tt>. If your changes are not 100% covered, go
+ back to step 6.
8. Commit and push your changes.
-9. Submit a pull request. Please do not include changes to the gemspec, version, or history file. (If you want to create your own version for some reason, please do so in a separate commit.)
+9. Submit a pull request. Please do not include changes to the gemspec,
+ version, or history file. (If you want to create your own version for some
+ reason, please do so in a separate commit.)
## Supported Ruby Versions
This library aims to support and is [tested against][travis] the following Ruby
Please sign in to comment.
Something went wrong with that request. Please try again.