INFO Skipping configuration for protected branch...

[stefkiourk]

I am changing the config.toml file to enable/disable different properties of auth and storage. However, I'm getting the message "INFO Skipping configuration for protected branch..." when I'm pushing the changes to main. I've tried creating another branch, which correctly picks up and reflects the changes, however when merging back to main, I get the same message. Example property: under [auth], enable_anonymous_sign_ins = true.

If "main" is my production branch, and I would like a change in the config, why would it skip it and consider it protected, even with normal PR merges? In case I am misunderstanding the process, how would one go about changing project configuration via Supabase branches?

Thank you.