I would suspect there are a non-trivial number of repos that do force pushes, including overwriting tags:
2024/10/05 17:34:27 command [git --git-dir /data/.sourcebot/repos/github.com/JetBrains/intellij-community.git fetch origin --prune] failed: exit status 1
! [rejected] idea/191.7141.44 -> idea/191.7141.44 (would clobber existing tag)
In those scenarios, what sourcebot believes is the tag will not square up with the upstream's idea of the tag
I actually checked their issue tracker and surprisingly there doesn't seem to be an issue for influencing that behavior. So in that way, it's great you have a fork
If you want me to try and open the issue with them, let me know
I would suspect there are a non-trivial number of repos that do force pushes, including overwriting tags:
In those scenarios, what sourcebot believes is the tag will not square up with the upstream's idea of the tag
I actually checked their issue tracker and surprisingly there doesn't seem to be an issue for influencing that behavior. So in that way, it's great you have a fork
If you want me to try and open the issue with them, let me know