pan3793 commented on PR #699: URL: https://github.com/apache/spark-website/pull/699#issuecomment-4957854254
@nchammas, thank you for working on this area, I agree that the current spark-website repo is a disaster ... some ideas and experience from maintaining other ASF project website repos might be helpful: 1. use `master` branch to track only the source code (if we want to keep the history, might need to use the git command to rewrite the whole history and filter out the compiled output files) 2. leave the `asf-site` branch to track the compiled output (keep it orphaned, no need to track history to keep the size under control) 3. when pushing code to `master`, trigger a workflow to build and push the output to the `asf-site` if we agree with this direction, then: 1. Spark PMC needs to ask the infra team to change the default branch to `master` 2. @nchammas you can debug that on your forked repo first, and compare the differences between the auto-generated `asf-site` (your forked repo) and the current `asf-site` (apache upstream) -- 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]
