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 few packages in my oraganization which we want to give read access to our collaborate third party to use, but according to the policy of our company, we can't let anyone but our employee being added to the organizations, according to this quote from Github Docs
If your package is private or internal and scoped to an organization, then you can only give access to other organization members or teams.
I think it's not possible to just add those developer into our package settings, also we wouldn't want our packages to go to public as we are not ready yet,
I also tried to publish our packages to other scoped account, but there will be one problem is that we will have a lot of dependencies inside one packages, let's say @orgA/packageA will import @orgA/packageB, @orgA/packageC, in order to make sure it will not try to download anything from @orga , we will need to change all the scope which will take a lot of effort and will be hard to maintain.
So is there a way for use to let someone not in our org to access the org scoped github packages ? or maybe choose other registry ?
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 few packages in my oraganization which we want to give
read
access to our collaborate third party to use, but according to the policy of our company, we can't let anyone but our employee being added to the organizations, according to this quote from Github DocsI think it's not possible to just add those developer into our package settings, also we wouldn't want our packages to go to public as we are not ready yet,
I also tried to publish our packages to other scoped account, but there will be one problem is that we will have a lot of dependencies inside one packages, let's say @orgA/packageA will import @orgA/packageB, @orgA/packageC, in order to make sure it will not try to download anything from @orga , we will need to change all the scope which will take a lot of effort and will be hard to maintain.
So is there a way for use to let someone not in our org to access the org scoped github packages ? or maybe choose other registry ?
Beta Was this translation helpful? Give feedback.
All reactions