You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have cloned a bare repo from some BitBucket repository,
modified it with filter-repo to get rid of some commits in the history,
and tried to push the result (git push --mirror). This fails.
Closer to the problem, the command: git push origin --force 'refs/replace/*'
fails. Output is like
! [remote rejected] refs/replace/fffde5e1ab13d1fcc288ef5f64bdbdf9701d21f2 -> refs/replace/fffde5e1ab13d1fcc288ef5f64bdbdf9701d21f2 (pre-receive hook declined)
Is this build-in behavior of BitBucket (release 7.17)?
Is it possible to deactivate this hook (that I did not find yet)?