Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
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