mercurial - Is it safe to remove bundles in strip-backup folders? -

mercurial - Is it safe to remove bundles in strip-backup folders? -

recently have rewrote lot of history (forgive me father, have sinned). our old repository had lot of sensitive info unnecessary merges (up 20 anonymous branches running simultaneously , beingness merged indiscriminately), have striped several commits, pruned dead branches, rebased / squashed commits, rolled unnecessary merges, created bookmarks, etc.

we have clean repo. have run unitary tests along several revisions create sure haven't broke import. yesterday i've forked old repo (for backup purposes) , pushed clean repository upstream. little team , synchronizing changes not problem, every developer in team working new repo.

anyway, local repository have .hg/strip-backup folder of around 2 gigabytes. able understand, folder contains backup bundles every 1 of destructive commands have run. no longer need those.

my question is: safe remove bundles within .hg/strip-backup? or corrupt local repository if delete files?

bonus question: there built-in mercurial command remove backups or should utilize rm .hg/strip-backup/*?

yes, safe remove whole folder. info contained in folder not relevant repo.

as bonus answer, best alternative clean-up cache folders re-clone repo. doing allows start fresh , temporary files left on base of operations repo. replace original repo cloned repo , won't have bother history of temporary files while.

mercurial