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 an organization in which i have private repositories for my packages. Ive published the packages to that organization and linked them to their respective repository automatically using workflows. Now i have an issue which is that the workflows in my repositories cant install the packages from other repositories and prevent the workflow from running successfully. I'd like to not use PATs/organization secrets since those can only be used on public repositories without a paid plan. How would i accomplish this?
Beta Was this translation helpful? Give feedback.
All reactions