Xavier Morel ec01523875 [IMP] runbot_merge: prune repo during maintenance ... The weekly maintenance would not prune refs. This is not an issue on odoo/odoo because development branches are in a separate repository, thus never fetched (we push to them but only using local commits and remote refs). However on repos like odoo/documentation the reference and development branches are collocated, the lack of pruning thus keeps every development branch alive locally, even years after the branch has been deleted in the repository. By pruning remote-tracking refs before GC-ing, we should have cleaner local clones, and better packing.		2024-08-05 09:03:39 +02:00
..
__init__.py	[ADD] runbot_merge: delete scratch branches when a branch is disabled	2023-08-31 09:07:01 +02:00
cleanup_scratch_branches.py	[IMP] rubnbot_merge: avoid triggering every cron on every test	2024-08-05 08:03:56 +02:00
cleanup_scratch_branches.xml	[ADD] runbot_merge: delete scratch branches when a branch is disabled	2023-08-31 09:07:01 +02:00
git_maintenance.py	[IMP] runbot_merge: prune repo during maintenance	2024-08-05 09:03:39 +02:00
git_maintenance.xml	[CHG] *: move repo cache from forwardbot to mergebot	2023-08-25 15:04:48 +02:00