+1, when you are working with Xata studio, maybe you open a suggested link in the browser that is for main, you don't double check the branch name considering it is your development one, and changes apply directly to production (eg I have accidentally deleted a db without any warning it was main)

Agree with Marcus Collier. Additionally, it would be great if a protected branch also requires an unlock of the data explorer to avoid inadvertent changes of production data.

This! I have done this too many times, then confused why my changes aren't syncing. :( Bonus points if you can protect other branches, but the ability to force the main branch to only allow schema changes via migrations is a bit of a necessity. Hell, I don't even need the ui to change, just a failure with a vague error message that you are modifying main would be fantastic!