jorisvandenbossche edited a comment on pull request #173: URL: https://github.com/apache/arrow-site/pull/173#issuecomment-1000379659
> Concern: apache/arrow-site repository size will be increased steadily. We may need to remove the previous commit to update dev docs (only if the previous commit is an update dev docs commit) before we update dev docs. Yes, this is indeed a problem (I raised a similar concern when adding the multiple versions of the docs, as that also steadily increases the repo size). For the dev docs specifically, we of course only need to have the latest version and can thus overwrite / clean-up the git history to avoid increasing the repo size. The options I was thinking about: - In the action, remove the history of just the dev docs directory with something like https://github.com/newren/git-filter-repo/. This rewrites history and thus requires force pushing from inside the action. - In the action, we could also completely re-initialize the asf-site branch from the current content + updated dev docs (in the idea that we mostly care about history in the mater branch, and less so in the asf-site branch?). But similarly as above, this requires force pushing from inside the action (so probably not much advantage for this option compared to the one above) - Keep the action as is (additional commit, so no need to force push), but from time to time clean-up the asf-site branch and force push manually (we could have a similar script to remove the history in the dev docs directory) Your idea of removing the previous commit to update dev docs (only if the previous commit is an update dev docs commit) could also be an option, but that will miss some of those commits, and also requires force pushing. I was a bit hesitant to take any option that requires a force push (so didn't yet add anything in this PR, leaving the manual clean-up from time to time), but maybe that's not actually a problem? -- 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]
