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
Two years ago I spent a lot of time exploring GitHub packages and actions. At that time I found out that packages are associated with a repository. This meant that running actions in
RepoA
that build projects that pull packages held inRepoB
, required some clumsy extra authentication steps, steps that were not needed for running similar build inRepoB
. Builds inRepoB
that pull packages fromRepoB
require simpler authentication.I asked about the possibility of storing packages at the organization level rather than at the repo level and there was some talk about the requirement being recognized but nothing imminent planned.
Today I revisited this subject and read this in the docs:
So has this feature been introduced? it really isn't clear to me, I'm specifically interested in Nuget packages.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions