hacker_news¶ ↑

Description goes here.

Contributing to hacker_news¶ ↑

Check out the latest master to make sure the feature hasn’t been implemented or the bug hasn’t been fixed yet
Check out the issue tracker to make sure someone already hasn’t requested it and/or contributed it
Fork the project
Start a feature/bugfix branch
Commit and push until you are happy with your contribution
Make sure to add tests for it. This is important so I don’t break it in a future version unintentionally.
Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Name		Name	Last commit message	Last commit date
Latest commit History 25 Commits
lib		lib
test		test
.document		.document
.gitignore		.gitignore
Gemfile		Gemfile
Gemfile.lock		Gemfile.lock
LICENSE.txt		LICENSE.txt
README		README
README.rdoc		README.rdoc
Rakefile		Rakefile
VERSION		VERSION
hacker_news.gemspec		hacker_news.gemspec