Replies: 3 comments 1 reply
-
I don't thing caching system0wide paths like A good approach (i think) would be to install Exo into a directory like
With this you could: avoid permission issues, cli is cached between workflows and you control where it resides and when it updates. |
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.
-
if I'm not mistaken, you cannot cache |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Question
What GitHub Actions topic or product is this about?
Actions Cache
Discussion Details
In a workflow, I need to use the Exo CLI, which is installed at
/usr/bin/
.Is there a way to cache it so I don't have to reinstall it every time I run the workflow?
I tried
But the runner doesn't have access to that path.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions