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)?
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events