Add metadata for rubygems.org #7435
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
m-nakamura145
force-pushed
the
update-gemspec
branch
from
943f9f8
to
fd3d266
Compare
hsbt
reviewed
Jan 30, 2024
| "source_code_uri" => "https://github.com/rubygems/rubygems", | ||
| "bug_tracker_uri" => "https://github.com/rubygems/rubygems/issues", | ||
| "changelog_uri" => "https://github.com/rubygems/rubygems/blob/master/CHANGELOG.md", | ||
| "funding_uri" => "https://rubycentral.org/#/portal/signup", |
There was a problem hiding this comment.
@indirect I'm not sure this is correct URI for funding Ruby Central. Can you look this?
There was a problem hiding this comment.
Yes, that is the correct URI for the membership signup page. I don't know why, but Ghost uses javascript to show the signup page over the regular home page :(
deivid-rodriguez
pushed a commit
that referenced
this pull request
Feb 5, 2024
Add metadata for rubygems.org (cherry picked from commit 7cb43e2)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What was the end-user or developer problem that led to this PR?
There were few metada settings on rubygems.org.
What is your fix for the problem, implemented in this PR?
This PR adds metadata for rubygems.org
Make sure the following tasks are checked