From d18da6b3f6ffe45c254ab68107c1165db2fe7b91 Mon Sep 17 00:00:00 2001
From: Matt C <41025489+mcummings128@users.noreply.github.com>
Date: Mon, 18 May 2026 15:24:25 -0400
Subject: [PATCH] Update notes on push event behavior in workflows

Note that workflows can be triggered by pushes to non-default branches.
---
 .../workflows-and-actions/events-that-trigger-workflows.md     | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md b/content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md
index 2f38e2ff8ccb..c312d06badcc 100644
--- a/content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md
+++ b/content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md
@@ -844,6 +844,9 @@ on:
 > [!NOTE]
 > When a `push` webhook event triggers a workflow run, the Actions UI's "pushed by" field shows the account of the pusher and not the author or committer. However, if the changes are pushed to a repository using SSH authentication with a deploy key, then the "pushed by" field will be the repository admin who verified the deploy key when it was added it to a repository.
 
+> [!NOTE]
+> You can use `push` to trigger a workflow that has not been merged to the default branch. This can be useful when you want to test a workflow but cannot merge it into the default branch.
+
 ### Running your workflow only when a push to specific branches occurs
 
 You can use the `branches` or `branches-ignore` filter to configure your workflow to only run when specific branches are pushed. For more information, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore).