Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
r? @brandur-stripe
cc @stripe/api-libraries
I wanted to test GitHub's new Package Registry feature and publish the latest stripe-ruby gem there. We need to add a custom
github_repo
entry to the metadata, because otherwise GitHub uses the gem's name as the repository's name, which in our case causes it to fail because the gem is calledstripe
and the repository is calledstripe-ruby
.While I was at it, I also added standard metadata as documented on https://guides.rubygems.org/specification-reference/#metadata.