I think it's a critical one, we need a way to protect our repositories never broken by unintentional commits.
Git has some learning cruves, it's difficult to let every memebers fully understand kinds of git usage. And it does NOT make sense to squash, amend even eliminate pushed/published commits. It will cause inconsistent state in distributed repos.
And it should be default behavior(deny non fast-forward commits) of git repo in bitbucket.
Do you know any workaround of it? How about re-pushing my repo to an empty repository
with 'denyNonFastForwards' flag in my local repository?
I will be honest, I know it won't happen in the next 3-4 months, we are just swapped with what we are currently trying to do.
After that it is hard to say. If there is a lot of interest on this issue it will make a difference but this is the first time the feature has been requested. So I am not sure there is a wide-spread desire for this.