snazy commented on PR #2006: URL: https://github.com/apache/polaris/pull/2006#issuecomment-3047791792
I wonder whether it's not easier to just copy the README.md file from `helm/polaris` to `site/content/in-dev/unreleased` when it's generated. The workflow for releases is to take what's in `site/content/in-dev/unreleased` and push it to the [`versioned-docs`](https://github.com/apache/polaris/tree/versioned-docs) branch. With a virtual mount, the helm readme would not be present. Orthogonal to this PR, I realized that the Helm README.md is generated, but there's nothing that guarantees that the file is up to date. I think, it would be better to not track the generated README.md in Git or at least have a CI step that verifies that the README.md file is up to date (aka generate in CI and compare with the one in Git). WDYT? -- 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]
