This is an automated email from the ASF dual-hosted git repository. vy pushed a commit to branch deploySiteTargetPath in repository https://gitbox.apache.org/repos/asf/logging-site.git
commit 54267c6268a892efdd51e854aaf75149ceb5bdf5 Author: Volkan Yazıcı <[email protected]> AuthorDate: Wed Dec 31 11:43:47 2025 +0100 Set `target-path` to `content` in `deploy-site.yaml` --- .github/workflows/deploy-site.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/.github/workflows/deploy-site.yaml b/.github/workflows/deploy-site.yaml index 18ab4c97..fdb6eaea 100644 --- a/.github/workflows/deploy-site.yaml +++ b/.github/workflows/deploy-site.yaml @@ -43,6 +43,11 @@ jobs: whoami: ${{ github.ref_name }}-site-stg-out 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. + # Other `logging-*` repositories using `deploy-site-reusable.yaml` can continue using the default `target-path`. + # See https://issues.apache.org/jira/browse/INFRA-27533 + target-path: content deploy-site-pro: if: github.repository == 'apache/logging-site' && github.ref_name == 'main-site-pro' @@ -59,3 +64,8 @@ jobs: whoami: ${{ github.ref_name }}-out 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. + # Other `logging-*` repositories using `deploy-site-reusable.yaml` can continue using the default `target-path`. + # See https://issues.apache.org/jira/browse/INFRA-27533 + target-path: content
