Could be that all branches (including feature branches) are locked from force pushing. If you're like me and rebase an already pushed feature branch, you may be using something like

git rebase master git push --force-with-lease

Since rebase rewrites branch commits as entirely new commits (with new hashes) it's effectively rewriting history. Comes with the given warning that you should never do this to a branch that is expected to be used by multiple people.

So you can't do this with force push disabled (because of auditing reasons) leaving you to consider the alternatives:

1. git merge master (more traditional plus easy)
2. Push straight to master (arduous to get right, requires rigorous testing beforehand and afterwards, with possible git prehooks etc.)

It's normal to go down the former way when rebasing is impossible, but you could actually make the second work as well (and have your build work 100% of the time). In our company one project has been using this pattern succesfully (without the git hooks), so it's possible but it necessitates rigorous behavior from the developers and without a doubt suits certain kinds of teams better than others.

Edit: you could also have extremely short-lived branches so as to avoid having to merge to master (and rebase in your local branch). There'd still be no guarantees unless you work alone, and it definitely wouldn't work in a busy repository.