lhotari commented on PR #982: URL: https://github.com/apache/pulsar-site/pull/982#issuecomment-3472134591
> @lhotari ready to merge? @dave2wave No. Like in most cases, contributors haven't applied the changes to the documentation in the way that takes Docusaurus `docs` and `versioned_docs` into account. The PR reviewer should help in addressing this and possibly handle this on behalf of the PR author. For example, I recently handled this in this PR: https://github.com/apache/pulsar-site/pull/1050/commits/7330ea9ad1a2a3b462a3533addfd37609998999b . In some cases, a PR is opened with a change made a versioned_docs file and in some case docs file without changes to versioned_docs. There's some tooling and instructions at https://github.com/apache/pulsar-site?tab=readme-ov-file#updating-versioned-docs and https://pulsar.apache.org/contribute/document-contribution/. These instructions could be improved. The tooling should also be improved so that a change made to a versioned_doc could be applied to docs folder automatically. I was planning to add that to https://github.com/apache/pulsar-site/blob/main/scripts/docs-tool.sh for making pulsar-site PR reviewers easier or let PR contributors handle this with some tooling like it's already possible with `./scripts/docs-tool.sh apply_last_commit_to_versioned_docs` when you make the change to docs file and what the same change to be made to versioned_docs files. I just feel that I shouldn't be the one who takes care of all tasks in the project. I've done a lot of this mostly alone in the past 2 years. -- 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]
