This is an automated email from the ASF dual-hosted git repository. vy pushed a commit to branch siteFix2 in repository https://gitbox.apache.org/repos/asf/logging-site.git
commit 9a7d8a9bcec62774f458664dd7da9512e8cb89c9 Author: Volkan Yazıcı <[email protected]> AuthorDate: Fri Jan 9 16:10:44 2026 +0100 Remove redundant `target-path` in `deploy-site.yaml` --- .github/workflows/deploy-site.yaml | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/.github/workflows/deploy-site.yaml b/.github/workflows/deploy-site.yaml index fdb6eaea..18ab4c97 100644 --- a/.github/workflows/deploy-site.yaml +++ b/.github/workflows/deploy-site.yaml @@ -43,11 +43,6 @@ 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' @@ -64,8 +59,3 @@ 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
