From 38e5e4ed8f8cf0bd5ea81c2abeea7d6874af4fc0 Mon Sep 17 00:00:00 2001
From: Dan Rigby <114417+DanRigby@users.noreply.github.com>
Date: Tue, 6 Jun 2023 20:29:40 -0400
Subject: [PATCH] Add note on `/refs/` usage. (#37389)

Co-authored-by: Siara <108543037+SiaraMist@users.noreply.github.com>
---
 data/reusables/actions/reusable-workflow-calling-syntax.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/reusables/actions/reusable-workflow-calling-syntax.md b/data/reusables/actions/reusable-workflow-calling-syntax.md
index 436bdccba0..3fcebb36e9 100644
--- a/data/reusables/actions/reusable-workflow-calling-syntax.md
+++ b/data/reusables/actions/reusable-workflow-calling-syntax.md
@@ -1,4 +1,4 @@
 * `{owner}/{repo}/.github/workflows/{filename}@{ref}`{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} for reusable workflows in {% ifversion fpt %}public and private{% elsif ghec or ghes > 3.7 or ghae > 3.7 %}public, internal and private{% else %}public and internal{% endif %} repositories.
 * `./.github/workflows/{filename}` for reusable workflows in the same repository.{% endif %}
 
-`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)." {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}If you use the second syntax option (without `{owner}/{repo}` and `@{ref}`) the called workflow is from the same commit as the caller workflow.{% endif %}
+`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)."{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} If you use the second syntax option (without `{owner}/{repo}` and `@{ref}`) the called workflow is from the same commit as the caller workflow.{% endif %} Ref prefixes such as `refs/heads` and `refs/tags` are not allowed.