GitHub Action from repo a clone repo b #40792
Replies: 2 comments
-
The main alternative is to create a PAT with the required access, and use |
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 there,
I have my code in a private repo (A), and some libs/modules hosted in other private repos (B, C, D, etc). The only way I found to make this work is by adding the SSH private key on each step that needs to access repo B (tbh, this doesn't feel that safe)
It's similar to this person's case:
https://stackoverflow.com/a/70283191/2868547
It's quite annoying to keep repeating the same thing since I've quite a few steps that need to access the other private repos. Is there a better/easy/safer way to do that?
Beta Was this translation helpful? Give feedback.
All reactions