What happens when the creator force-pushes a new version with everything removed

[Xyndra]

There have been a lot of situations where repos get deleted like this https://github.com/tachiyomiorg/extensions https://github.com/PabloMK7/citra where there is a force-pushed old/empty version. How is this handled here?

[arunavo4]

@Xyndra Hey so this is something I did not prepare for so currently mirror will match that and can wipe it. So, I am working on a PR where we can do a snapshot locally from which repos can be restored.

[arunavo4]

Implemented in PR #190: #190

This adds pre-sync snapshot protection (bundle backup before mirror-sync) with configurable fail-closed behavior to prevent destructive force-push rewrites from removing recoverable history.

[Xyndra]

My Gitea is more than 100 GiBs big since mirroring my stars. Duplicating those for backups seems nonsensical. This is nice to be able to get configured for certain repos, but it would be nice to have a way to either block force pushes fully, requiring manual approval to sync, or to have a _<branch>_backup_<timestamp> branch get created in the background