How does gickup deal with force pushes to upstream (source)?

[kravemir]

I am searching for a git backup tool, where I would have confidence, that:

• what was backed up before, remains backed up after re-execution of the tool:
  • protect against source corruption,
  • new backup doesn't erase history,
  • ability to go back in time is retained even if source repository had purged all/some of its commits,
• when backup runs, the current state of source is backed up:
  • new backup doesn't fail on conflicts between repository containing the backup, andthe source repository,
  • no manual intervention or conflict resolution is needed.

Does gickup cover the above in any way?

One approach to solve it is to create a new branch with old contents, if default branch force pushed in source repository, and then reset copy to upstream. I.e.:

1. create main-before-backup-[date-time] from last backed main (default branch),
2. force push upstream/main to destination/main.

I don't care about specific solution, as long as history is preserved, and backup still continues to function, and doesn't break.

[cooperspencer]

It doesn't handle force pushes well yet. One of the next things on my todo list. But what you can do is to enable zip and keep on the local backup. That creates a zip file of your repository and keeps as many backups as you configure. That way you can keep the original state of your repository.

https://cooperspencer.github.io/gickup-documentation/configuration/destination_docu/local