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

Cannot push to github registry #152

Open
ShockwaveNN opened this issue Apr 30, 2020 · 2 comments
Open

Cannot push to github registry #152

ShockwaveNN opened this issue Apr 30, 2020 · 2 comments
Labels

Comments

@ShockwaveNN
Copy link
Collaborator

Got

Pushing gem to https://rubygems.pkg.github.com/ONLYOFFICE...
The expected resource was not found.

Maybe releated to project name and gem slightly different (onlyoffice_api and onlyoffice_api_gem)
See some more info at
https://github.community/t5/GitHub-API-Development-and/Unable-to-push-RubyGem-to-Package-Registry-The-expected-resource/m-p/44599/highlight/true#M3939

@lukad
Copy link

lukad commented May 12, 2020

The onlyoffice_api_gem/onlyoffice_api naming mismatch also causes the links to the project homepage and source code to be wrong on the rubygems page. The homepage is currently set to "https://github.com/ONLYOFFICE/#{s.name}" but should probably just be hardcoded to the correct url: https://github.com/ONLYOFFICE/onlyoffice_api_gem/blob/d7b60aa516093337c47e571b702f36510700b30d/onlyoffice_api.gemspec#L13

@ShockwaveNN
Copy link
Collaborator Author

ShockwaveNN commented May 12, 2020

@lukad Yeah, agree to you.

Since I don't think that renaming repo to onlyoffice_api is good idea better to change official name of this gem

And since current name is not totally correct - API is for ONLYOFFICE CommunityServer project - I think new name should be something like onlyoffice-communityserver-api-gem (pretty long but totally accurate)

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

No branches or pull requests

2 participants