dengliming opened a new issue, #1152: URL: https://github.com/apache/shenyu-website/issues/1152
## Problem The [Website Deploy workflow](https://github.com/apache/shenyu-website/blob/main/.github/workflows/deploy.yml) runs on every `pull_request` and every push to `main`, including merged PRs. Its `Setup Python` and `Generate PDF` steps run unconditionally before `yarn build`. The [PDF generation script](https://github.com/apache/shenyu-website/blob/main/.github/scripts/generate-pdf.sh) installs Sphinx, TeX Live, Pandoc, and fonts, then generates both English and Chinese documentation PDFs. Repeating this work for every PR and merge adds CI overhead and makes website validation/deployment depend on PDF tooling and external downloads. ## Proposed change - Move PDF generation and its dependencies into a dedicated GitHub Actions workflow. - Trigger that workflow only through `schedule` and `workflow_dispatch`. A weekly schedule is a suggested starting point; maintainers can choose the interval. - Generate both language PDFs from `main` on scheduled runs and allow maintainers to regenerate them manually when needed. - Remove PDF generation and its dependency setup from the PR/main-push website workflow, while keeping the existing website build and deployment triggers. - Publish or persist the generated PDFs so ordinary website deployments continue to serve the latest successfully generated versions at the existing download URLs. Removing the generation step must not revert the published PDFs to stale repository copies or remove them. ## Acceptance criteria - Opening/updating a PR or pushing/merging to `main` does not install PDF-specific dependencies or regenerate PDFs. - Scheduled and manually dispatched runs generate both `apache_shenyu_docs_en.pdf` and `apache_shenyu_docs_zh.pdf`. - Newly generated PDFs become available through the existing website download links, and subsequent ordinary deployments preserve them. - A PDF-generation failure does not block normal PR website builds or main-branch website deployments. Related: #1143 mentions PDF build overhead as part of broader project hygiene; this issue specifically tracks changing PDF generation triggers and separating it from website CI. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
