djencks opened a new issue #733: URL: https://github.com/apache/camel-website/issues/733
The local/partial builds idea requires everyone working on the docs (hopefully all camel devs :-) to clone and pull the camel-website repo moderately often. The main branch is pretty tiny compared with the published site, and although it's possible to just clone a single branch it's rather tricky. It's confusing to pull and see a big update as the published site is completely replaced when there is no change in main. It's a pretty simple change to publish to a separate repo rather than a branch in the current repo. Publishing to a separate repo offers the ability to keep website history rather than only the current version (by squashing commits) without slowing down everything in sight, but whether to do that is a separate question. -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
