Replies: 2 comments
-
Hello, Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
🕒 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
Hello 👋 ,
I have a NPM package pushed to GitHub package registry with internal visibility in OrgA.
It's accessible in GitHub workflow of all OrgA repositories without any issue.
My company has another GitHub organization, OrgB that also want to use the NPM package in theirs repositories.
Can I give access to OrgB so that their GITHUB_TOKEN (in GitHub workflow) give access to OrgA NPM packages ?
Thanks 🙇♂️
Beta Was this translation helpful? Give feedback.
All reactions