nchammas commented on PR #696: URL: https://github.com/apache/spark-website/pull/696#issuecomment-4790742801
I agree most of the time we are looking at PRs. But it is still a big advantage IMO when the local git status, remote git history, and repo structure all show only source changes. It just makes the whole repository look and work more like a "normal" one, and there is no need to ever think about filtering out noise. I have been reading up on [.asf.yaml](https://github.com/apache/infrastructure-asfyaml/) and how we can test changes on a staging site (FYI: [we already have one](https://spark.staged.apache.org/)), automatically build the HTML, etc. I have a plan to get us to a source-only `master` branch, but it will require close coordination with a committer. The result will be a much better setup and workflow for this repo. On the other hand, I know this repo is not exactly the most exciting part of the project. So if you want to do something more conservative that is easier to review, I understand. -- 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]
