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 1/3] 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). From 75dcafb0bb2f241357975cf77ec36faf0d49ad9f Mon Sep 17 00:00:00 2001 From: Matt C <41025489+mcummings128@users.noreply.github.com> Date: Fri, 22 May 2026 16:04:00 -0400 Subject: [PATCH 2/3] Update notes on workflow triggers for pushes Reworded from suggestion made yesterday (5-21-26) in PR --- .../workflows-and-actions/events-that-trigger-workflows.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) 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 c312d06badcc..8ce8d4908d98 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 @@ -832,7 +832,7 @@ jobs: > * The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the API. For information, see [AUTOTITLE](/graphql/reference/objects#commit) in the GraphQL API documentation or [AUTOTITLE](/rest/commits#get-a-commit). > * Events will not be created if more than 5,000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. -Runs your workflow when you push a commit or tag, or when you create a repository from a template. +Runs your workflow when you push a commit or tag, or when you create a repository from a template. This includes workflows that are not merged into the default branch. For more information, see [AUTOTITLE](actions/reference/workflows-and-actions/events-that-trigger-workflows#running-your-workflow-only-when-a-push-to-specific-branches-occurs)". For example, you can run a workflow when the `push` event occurs. @@ -844,9 +844,6 @@ 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). From 749b93188a78abed6f59340b7b37c778dae7e9d8 Mon Sep 17 00:00:00 2001 From: Sharra-writes Date: Fri, 22 May 2026 16:03:09 -0700 Subject: [PATCH 3/3] Apply suggestion from @Sharra-writes --- .../workflows-and-actions/events-that-trigger-workflows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 8ce8d4908d98..5fcddb934237 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 @@ -832,7 +832,7 @@ jobs: > * The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the API. For information, see [AUTOTITLE](/graphql/reference/objects#commit) in the GraphQL API documentation or [AUTOTITLE](/rest/commits#get-a-commit). > * Events will not be created if more than 5,000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. -Runs your workflow when you push a commit or tag, or when you create a repository from a template. This includes workflows that are not merged into the default branch. For more information, see [AUTOTITLE](actions/reference/workflows-and-actions/events-that-trigger-workflows#running-your-workflow-only-when-a-push-to-specific-branches-occurs)". +Runs your workflow when you push a commit or tag, or when you create a repository from a template. This includes workflows that are not merged into the default branch. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows#running-your-workflow-only-when-a-push-to-specific-branches-occurs). For example, you can run a workflow when the `push` event occurs.