How do I disable history rewriting? (rebase, forced commit)

[Yaron Kaplan]

I don't want this to happen:

$ git pull

[...]
+ b8e0d3a...848d220 v3_31_0 -> origin/v3_31_0 (forced update)
Already up-to-date.

 Because forced update means conflicts - and also you can't find who did it due to git shortcomings.

How do I disable this?

There used to be a way using branch permissions, mentioned here, but the options I see now don't include a way to disable history rewriting (screenshot included below).

Thanks in advance.

[Yaron Kaplan · Accepted solution]

Update: Apparently you need to put something in the Write Access field and only after that you can see the option to enable/disable history rewriting.

[jredmond]

You're looking at Bitbucket Cloud (screenshot) but you've linked to Bitbucket Server documentation. Please see https://confluence.atlassian.com/bitbucket/branch-permissions-385912271.html instead.

[Yaron Kaplan]

Thanks for your response.

However, the link you sent me also seems out of sync with actual service. The article mentions the Allow rewriting branch history option but I can't see it in the repository settings page.