You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDQuestion
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Question
Body
I was assuming when writing https://github.com/kaihendry/actions/blob/main/goredo/Dockerfile that I would be adding the "redo" binary to the workflow context, but I realise it's running in a Docker style context: https://github.com/kaihendry/prazefarm/actions/runs/13614164605/job/38055060389 and failing since m4/toc which are installed earlier in the workflow, aren't available.
Can you suggest how I best move forward here? Add m4/toc to my Dockerfile (not keen on this), write a "setup-goredo" action, but how?
The tricky thing is that
RUN ./goredo -symlinks
creates a bunch of symlinks!Beta Was this translation helpful? Give feedback.
All reactions