Is it possible to avoid using `git push -f` ?

[sihuan]

Hi, I'm building the uxplay-git package for the archlinuxcn repo. It uses the latest commit build and uses printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" as the version number. It looks like this repo sometimes does a git push -f which causes the commit count to fall back, which causes the version number to fall back and our users can't update (in fact our build bot refuses to push updates to the user because the new package looks "older") Is it possible to avoid using git push -f, please?

[fduncanh]

OK we heard you.

rebase + squash + push -f was being used to combine small updates to README.

[fduncanh]

@sihuan I am sorry, but I just had to do a git push -f again. (after an accidental very bad commit accident that needed immediate reversal)

I am trying not to do this any more, but sometimes things happen

[sihuan]

@sihuan I am sorry, but I just had to do a git push -f again. (after an accidental very bad commit accident that needed immediate reversal)

I am trying not to do this any more, but sometimes things happen

It's okay. I'm going to use the build date-commit hash as the package version number, so that won't be a problem.