Skip to content
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 project metadata to the gemspec #519

Merged
merged 1 commit into from Nov 30, 2020
Merged

Add project metadata to the gemspec #519

merged 1 commit into from Nov 30, 2020

Conversation

orien
Copy link
Contributor

@orien orien commented Nov 29, 2020

Add bug_tracker_uri, changelog_uri, documentation_uri, homepage_uri, source_code_uri, and wiki_uri to the gemspec metadata.

These project metadata will facilitate easy access to project information. The URI will be available on the Rubygems project page, via the rubygems API, and the gem and bundle command-line tools with the next release.

As per https://guides.rubygems.org/specification-reference/#metadata,
add metadata to the gemspec file. This'll allow people to more easily
access the source code, raise issues and read the changelog. These
bug_tracker_uri, changelog_uri, documentation_uri, homepage_uri
source_code_uri, and wiki_uri links will appear on the rubygems page at
https://rubygems.org/gems/listen and be available via the rubygems API
after the next release.
@ColinDKelley
Copy link
Collaborator

@orien Thank you for the PR. Just curious: is there a reference list for those specific metadata keys?

@orien
Copy link
Contributor Author

orien commented Nov 30, 2020

@ColinDKelley
Copy link
Collaborator

ColinDKelley commented Nov 30, 2020

Oh, ok! I had already clicked through to that list but it seemed to be just some random examples; I didn't realize it was a reference list for the full set of supported keys. But I guess it is.

I'll merge now and release as v3.3.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants