On 7/9/2020 7:21 AM, Derrick Stolee wrote: > On 7/8/2020 7:57 PM, Emily Shaffer wrote: >> On Tue, Jul 07, 2020 at 02:21:14PM +0000, Derrick Stolee via GitGitGadget wrote: >>> An expert user could set up scheduled background maintenance themselves with >>> the current series. I have the following crontab data set up to run >>> maintenance on an hourly basis: >>> >>> 0 * * * * git -C /<path-to-repo> maintenance run --no-quiet >>/<path-to-repo>/.git/maintenance.log >> >> One thing I wonder about - now I have to go and make a new crontab >> (which is easy) or Task Scheduler task (which is a pain) for every repo, >> right? >> >> Is it infeasible to ask for 'git maintenance' to learn something like >> '--on /<path-to-repo> --on /<path-to-second-repo>'? Or better yet, some >> config like "maintenance.targetRepo = /<path-to-repo>"? Sorry that I missed this comment on my first reply. The intention is that this cron entry will be simpler after I follow up with the "background" part of maintenance. The idea is to use global or system config to register a list of repositories that want background maintenance and have cron execute something like "git maintenance run --all-repos" to span "git -C <repo> maintenance run --scheduled" for all repos in the config. For now, this manual setup does end up a bit cluttered if you have a lot of repos to maintain. Thanks, -Stolee
