Replies: 2 comments 1 reply
-
After looking into this a bit, I believe you can replicate what you need using environment variables with If we weren't using composite actions, it would be simpler and covered by the README with Now, as you mention, composite actions can't directly use secrets so you can't declare it as a secret. However, you could declare it as an environment variable. There are two ways you can provide the env variable to Option 1: Provide it from an env variable on your machine (recommended)Recommending this as it's likely safer and has less chance of accidentally exposing the value in your SCM. First, define the value: Then, run your workflow with: Option 2: Provide it from a fileFollowing the sample here. If you do this, make sure to Set your
Run your workflow with: Example using this in the workflowIn your flow, you could do this (following example from the README on how to skip/do actions based on whether in GHA or in Act):
Testing setupClick meDirectory structure
test.yml
test-composite/action.yml
|
Beta Was this translation helpful? Give feedback.
-
It is possible that the documentation is not clear enough about this
|
Beta Was this translation helpful? Give feedback.
-
composite actions cant directly use
${{secrets.GITHUB_TOKEN}}
, but they can use${{github.token}}
(it might be a blanket dsl guard onsecrets.*
)I'm unable to find how i can simulate
${{github.token}}
withnetkos/act
Beta Was this translation helpful? Give feedback.
All reactions