This is an automated email from the ASF dual-hosted git repository.
snazy pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/polaris.git
The following commit(s) were added to refs/heads/main by this push:
new b4951c0a7 Update triggers in "Hugo Site" workflow (#3518)
b4951c0a7 is described below
commit b4951c0a75034e5c97bf904ecceeef5776dcf700
Author: Robert Stupp <[email protected]>
AuthorDate: Sat Jan 24 09:40:37 2026 +0100
Update triggers in "Hugo Site" workflow (#3518)
The `site.yml` workflow is currently triggered in the following scenarios:
1. A push to the `main` branch, using the state of the site and the
workflow as on `main`.
2. A push to a `release/*`branch, using the state of the site and the
workflow as on that release branch.
Notice that workflows get the repo state (from the checkout actions) and
the workflow state as its on that particular branch.
Put in other words: if we'd have a change to some old `release/1.0.x`
branch, the web site would be updated as it is defined on that `release/1.0.x`
branch, which is wrong and not the intended behavior.
This change updates the workflow triggers to only run for pushes to the
`main` branch, plus PRs against the `main` branch and when called from another
workflow.
This is part of #3516
---
.github/workflows/site.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/.github/workflows/site.yml b/.github/workflows/site.yml
index b4dc4bd5f..77fa75ef6 100644
--- a/.github/workflows/site.yml
+++ b/.github/workflows/site.yml
@@ -20,9 +20,9 @@
name: "Hugo Site"
on:
push:
- branches: [ "main", "release/*", "versioned-docs" ]
+ branches: [ "main" ]
pull_request:
- branches: [ "main", "release/*" ]
+ branches: [ "main" ]
jobs:
site:
