You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question regarding the authentication for installing the gem published in the GitHub Package Registry. The repository is open, and the gem package is open. But users still need to provide credentials. I know that this behavior according to the documentation. But I think it's not okay.
Question: What is the reason to ask credentials of users to install an open gem with open source code? Thanks!
PackagesHost your dependencies, libraries, and production-ready code, right from your repositoryQuestion
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Question
Body
I have a question regarding the authentication for installing the gem published in the GitHub Package Registry. The repository is open, and the gem package is open. But users still need to provide credentials. I know that this behavior according to the documentation. But I think it's not okay.
Question: What is the reason to ask credentials of users to install an open gem with open source code? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions