From d2a78f18acd539fd4237073368c33e072cd46b3d Mon Sep 17 00:00:00 2001 From: Lachlan Heywood Date: Fri, 4 Oct 2024 13:25:52 -0400 Subject: [PATCH] Add context information for `jobs..uses` As far as I can tell, this property does not have access to any context and needs to be a statically defined string. If this is incorrect, it'd be great to have some clarification here. --- .../accessing-contextual-information-about-workflow-runs.md | 2 +- data/reusables/actions/reusable-workflow-calling-syntax.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md b/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md index a9855f035f2d..57e2ee1d9ff5 100644 --- a/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md +++ b/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md @@ -88,7 +88,7 @@ Different contexts are available throughout a workflow run. For example, the `se In addition, some functions may only be used in certain places. For example, the `hashFiles` function is not available everywhere. -The following table indicates where each context and special function can be used within a workflow. Unless listed below, a function can be used anywhere. +The following table lists the restrictions on where each context and special function can be used within a workflow. The listed contexts are only available for the given workflow key, and may not be used anywhere else. Unless listed below, a function can be used anywhere. | Workflow key | Context | Special functions | | ---- | ------- | ----------------- | diff --git a/data/reusables/actions/reusable-workflow-calling-syntax.md b/data/reusables/actions/reusable-workflow-calling-syntax.md index 3b3312822818..ddda9da4e2f7 100644 --- a/data/reusables/actions/reusable-workflow-calling-syntax.md +++ b/data/reusables/actions/reusable-workflow-calling-syntax.md @@ -3,4 +3,4 @@ In the first option, `{ref}` can be a SHA, a release tag, or a branch name. If a release tag and a branch have the same name, the release tag takes precedence over the branch name. Using the commit SHA is the safest option for stability and security. For more information, see "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)." -If you use the second syntax option (without `{owner}/{repo}` and `@{ref}`) the called workflow is from the same commit as the caller workflow. Ref prefixes such as `refs/heads` and `refs/tags` are not allowed. +If you use the second syntax option (without `{owner}/{repo}` and `@{ref}`) the called workflow is from the same commit as the caller workflow. Ref prefixes such as `refs/heads` and `refs/tags` are not allowed. You cannot use contexts or expressions in this keyword.