-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More documentation is needed on how variables/secrets are rendered/scoped across reusable workflows & actions #931
Comments
Are there any updates on this Issue? |
not really :( |
needs answer of this. please. this has been about a year. |
I also think this is much needed. |
How can I access the organization-secrets in a called workflow of the same repo? |
Hi @anderssonw, any idea why |
@sinux-l5d I'm not affiliated with GitHub, just ran into the same problem and found the documentation earlier. No idea why it works this way. |
@bobleujr Could you please share the document? This issue is still not resolved. |
Hi community, I feel the need for better documentation on how variables are available, scoped, rendered across reusable workflows, actions, etc. It's almost a shot in the dark trying to get our values running through workflows.
Example 1 -
${{ github.workspace }}
In the workflow definition,
${{ github.workspace }}
renders to nothing, exampleHowever, in the reusable workflow
.../.github/workflows/template.yaml@pipelines
, it renders the correct pathThen in the documentation for available environment variables, we see GITHUB_WORKSPACE as an available variable. How does
GITHUB_WORKSPACE
becomes thisgithub.workspace
, on which occasions? When are they available? Where? (this goes for everything github.*Example 2 - Organization secrets
As stated here: actions/runner#1413
Organization-level secrets aren't available in the caller workflow. But repo-specific repos are!
Example 3 - env at root is not available at any moment in the caller workflow
In the caller workflow, if
env
is defined at the root level of the framework, values aren't achievable anywhere within thejobs.<job_id>.with
.Trying to access from the job definition is also invalid. * and doesn't allow for reuse of variables in different
uses
.I mean, the list goes on. I have an entire document on how to rig solutions to get these values through, but I don't see it anywhere on the documentation. For instance, Azure DevOps has differences for
![image](https://user-images.githubusercontent.com/6935646/139484096-ec9df8e3-0af3-44eb-aad3-4df39847ad12.png)
${{ var }}
[ var ]
$(var)
.The text was updated successfully, but these errors were encountered: