jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-25 02:17:36 -05:00
Code Issues Projects Releases Wiki Activity

Add note for actions var overwrite. (#57748)

Browse Source
This commit is contained in:
Tingluo Huang
2025-10-01 10:51:01 -04:00
committed by GitHub
parent d7c0d0d30c
commit b961b6ae9d
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
content/actions/reference/workflows-and-actions/variables.md
View File

@@ -91,6 +91,9 @@ When you set an environment variable, you cannot use any of the default environm
If a variable with the same name exists at multiple levels, the variable at the lowest level takes precedence. For example, if an organization-level variable has the same name as a repository-level variable, then the repository-level variable takes precedence. Similarly, if an organization, repository, and environment all have a variable with the same name, the environment-level variable takes precedence.
> [!NOTE]
> Environment-level variables are only available on the runner after the job starts executing. This means that environment-level variables won't overwrite variables in the `env` and `vars` contexts.
For reusable workflows, the variables from the caller workflow's repository are used. Variables from the repository that contains the called workflow are not made available to the caller workflow.
## Limits for configuration variables