New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add description to gemspec #1205

Merged
merged 1 commit into from Nov 9, 2018

Conversation

2 participants
@lostapathy
Contributor

lostapathy commented Nov 9, 2018

This adds a short description to the gemspec.

Specifically, I wanted to add the word "Elasticsearch" so that this gem is more discoverable on RubyGems by potential users who need an Elasticsearch client.

Obviously just my first draft of the text trying to make the gem easier to discover, please improve as you see fit.

@ankane

This comment has been minimized.

Owner

ankane commented Nov 9, 2018

Hey @lostapathy, great idea 👍 Can’t believe I missed that (facepalm).

I usually keep the gem summary and GitHub description synced, so how about adding “with Rails and Elasticsearch” to the summary?

@lostapathy lostapathy force-pushed the lostapathy:gem_description branch from 2a85668 to aebdb9f Nov 9, 2018

@lostapathy

This comment has been minimized.

Contributor

lostapathy commented Nov 9, 2018

Sure - done! FWIW, I think rubygems.org will update that for you automagically when you publish a new gem if you put it in the gemspec description and/or summary. Been a while since I looked at the code.

@ankane ankane merged commit ddd8787 into ankane:master Nov 9, 2018

1 check was pending

continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
@ankane

This comment has been minimized.

Owner

ankane commented Nov 9, 2018

Thanks. Yeah, Rubygems uses the info from your latest release on the main gem page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment