morningman opened a new pull request, #3645:
URL: https://github.com/apache/doris-website/pull/3645

   Dev docs migrated to the docs-next plugin and the legacy plugin runs with 
includeCurrentVersion: false, so docs/ and i18n/zh-CN/.../current/ were no 
longer being compiled. Remove the source trees plus all the CI / governance / 
i18n hooks that still referenced them.
   
   Deletions:
   - docs/ (1504 files), i18n/zh-CN/docusaurus-plugin-content-docs/current/ 
(1518 files), and current.json
   - sidebars.ts (legacy plugin sidebar; unused under includeCurrentVersion: 
false)
   - .github/workflows/check-legacy-docs-frozen.yml (legacy-only gate)
   - crowdin.yml (dead config; no workflow invokes Crowdin and target i18n/ja 
does not exist)
   - tools/maintainers.json + tools/check_review.py + 
.github/workflows/approve-check.yml (dormant maintainer-approval gate; the 
workflow was entirely commented out)
   
   Updates:
   - docusaurus.config.js: drop sidebarPath for the legacy plugin
   - .github/workflows/build-check.yml: drop dead docs/* / zh-current / 
sidebars.ts case branches
   - .github/workflows/manual-i18n-translate-workflow.yaml: default source_dir 
docs -> docs-next
   - .docs-governance/rules.yml + owners.yml: drop 'current' version, the docs 
/ zh-current content roots, related doc_type / sync_policy entries, and legacy 
paths in each owner block
   - scripts/docs-governance/{manifest,lint-i18n-sync}.js: drop legacy current 
branches from path resolution; STRONG_SYNC_VERSIONS no longer includes 'current'
   - local_build_docs.sh: stop populating legacy current dirs; only the 
versioned_docs reimport remains
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to