This is an automated email from the ASF dual-hosted git repository. vy pushed a commit to branch siteFix in repository https://gitbox.apache.org/repos/asf/logging-site.git
commit ca6afba15e363b677a0c0a48015884ea601f5448 Author: Volkan Yazıcı <[email protected]> AuthorDate: Fri Jan 9 15:29:43 2026 +0100 Fix `deploy-site.yaml` as suggested by @Humbedooh[1] [1] https://the-asf.slack.com/archives/CBX4TSBQ8/p1767880006535609?thread_ts=1767877560.723049&cid=CBX4TSBQ8 --- .github/workflows/deploy-site.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/deploy-site.yaml b/.github/workflows/deploy-site.yaml index fdb6eaea..48806a5e 100644 --- a/.github/workflows/deploy-site.yaml +++ b/.github/workflows/deploy-site.yaml @@ -41,7 +41,7 @@ jobs: staging: profile: ~ whoami: ${{ github.ref_name }}-site-stg-out - subdir: content/ + subdir: content target-branch: ${{ github.ref_name }}-site-stg-out # For some unknown reason, `target-path` needs to be `content`. # Fortunately, it is only `logging-site` that needs to implement this hack. @@ -62,7 +62,7 @@ jobs: asf-yaml-content: | publish: whoami: ${{ github.ref_name }}-out - subdir: content/ + subdir: content target-branch: ${{ github.ref_name }}-out # For some unknown reason, `target-path` needs to be `content`. # Fortunately, it is only `logging-site` that needs to implement this hack.
