Josh Steadmon <steadmon@xxxxxxxxxx> writes: > Regardless of what happens with the job-runner, I would like to see a > top-level command that performs a single iteration of all the > recommended maintenance steps, with zero configuration required, on a > single repo. This gives an entry point for users who want to manage > their own maintenance schedule without running a background process. > ... >> Unix users will be unhappy with us if we use our own scheduling system >> when cron is available. They will expect us to reimplement those >> features and they will complain if we do not. While I cannot name >> names, there are a nontrivial number of large, enterprise monorepos that >> run only on macOS and Linux. > > Speaking purely as a user, I agree with this point. This is why I want a > single-iteration top-level maintenance command. Yes, well said. It exactly is what "git gc" was meant to be. To put it differently, if you asked any non-novice end-user if there is one single command that s/he would use to keep a repository healthy, it is very likely that the answer would be "git gc". And having such a single point of entry would be a good thing. Thanks.
