From 25cdb78153d8fcf19db18720c0948c3edff874c8 Mon Sep 17 00:00:00 2001 From: Pablo Collazo Collarte Date: Fri, 21 Nov 2025 09:27:02 +0100 Subject: [PATCH 1/2] feat: Update ref-description.md --- data/reusables/actions/ref-description.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/actions/ref-description.md b/data/reusables/actions/ref-description.md index 046807edef02..55364ac1c021 100644 --- a/data/reusables/actions/ref-description.md +++ b/data/reusables/actions/ref-description.md @@ -1 +1 @@ -The fully-formed ref of the branch or tag that triggered the workflow run. For workflows triggered by `push`, this is the branch or tag ref that was pushed. For workflows triggered by `pull_request`, this is the pull request merge branch. For workflows triggered by `release`, this is the release tag created. For other triggers, this is the branch or tag ref that triggered the workflow run. This is only set if a branch or tag is available for the event type. The ref given is fully-formed, meaning that for branches the format is `refs/heads/`. For pull requests events except `pull_request_target`, it is `refs/pull//merge`. `pull_request_target` events have the `ref` from the base branch. For tags it is `refs/tags/`. For example, `refs/heads/feature-branch-1`. +The fully-formed ref of the branch or tag that triggered the workflow run. For workflows triggered by `push`, this is the branch or tag ref that was pushed. For workflows triggered by `pull_request` that were not merged, this is the pull request merge branch. If the pull request was merged, this is the head branch. For workflows triggered by `release`, this is the release tag created. For other triggers, this is the branch or tag ref that triggered the workflow run. This is only set if a branch or tag is available for the event type. The ref given is fully-formed, meaning that for branches the format is `refs/heads/`. For pull requests events except `pull_request_target` that were not merged, it is `refs/pull//merge`. `pull_request_target` events have the `ref` from the base branch. For tags it is `refs/tags/`. For example, `refs/heads/feature-branch-1`. From 3bf4cfecf59b0a1ee1f362ba1943bc7a3780f583 Mon Sep 17 00:00:00 2001 From: Pablo Collazo Collarte Date: Fri, 21 Nov 2025 09:28:40 +0100 Subject: [PATCH 2/2] feat: Update ref_name-description.md --- data/reusables/actions/ref_name-description.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/actions/ref_name-description.md b/data/reusables/actions/ref_name-description.md index dd7b91d69524..46b2aee9954e 100644 --- a/data/reusables/actions/ref_name-description.md +++ b/data/reusables/actions/ref_name-description.md @@ -1 +1 @@ -The short ref name of the branch or tag that triggered the workflow run. This value matches the branch or tag name shown on {% data variables.product.prodname_dotcom %}. For example, `feature-branch-1`.

For pull requests, the format is `/merge`. +The short ref name of the branch or tag that triggered the workflow run. This value matches the branch or tag name shown on {% data variables.product.prodname_dotcom %}. For example, `feature-branch-1`.

For pull requests that were not merged, the format is `/merge`.