Skip to content

Clarify that vars context is unavailable in composite actions #46312

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.

Sign up for GitHub

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

Closed
imaloveabra wants to merge 1 commit into from
Closed

Clarify that vars context is unavailable in composite actions #46312

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion content/actions/reference/workflows-and-actions/contexts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -361,7 +361,8 @@ This example workflow shows how configuration variables set at the repository, e

> [!NOTE]
> Configuration variables at the environment level are automatically available after their environment is declared by the runner.

> [!NOTE]
> The `vars` context is not available inside a composite action. To use a repository variable inside a composite action, pass it as an `input` from the calling workflow. For example, pass `${{ vars.MY_VAR }}` as `with: my-var: ${{ vars.MY_VAR }}` in the calling workflow, then use `${{ inputs.my-var }}` inside the composite action.
{% data reusables.actions.actions-vars-context-example-usage %}

## `job` context
Expand Down
Loading