tisonkun commented on PR #286: URL: https://github.com/apache/pulsar-site/pull/286#issuecomment-1315551157
FWW, I think generated apidocs should gradually archive to `asf-site-next` branch so that we keep source code tidy. For example, I generate legacy C++ API doc and Python API doc at: * https://github.com/apache/pulsar-site/commit/d59ca05e263b50b68f37b69a071aca9eeaf9ecac * https://github.com/apache/pulsar-site/commit/d59ca05e263b50b68f37b69a071aca9eeaf9ecac But I don't have a clear idea on workflow to do this archive. We can do it manually for a while and find a proper way. Generate docs under the main branch has two advantages: * Simple preview; * Release manager doesn't have to understand how to commit API docs to the `asf-site-next` branch. -- 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]
