Hi @nogaman
I’m sorry that my answer was a little bit generic. I’ll try to be more specific.
I was referring to the idea that we do not plan to add any branch protections or branch restrictions from our side.
That means that any manager or developer can push to any branch that is connected to Crowdin. It’s expected that if you work with branches, you know how to work with branches, and push everything to the place where it should be pushed.
You can either not connect the master and work with only development branches, or simply notify your developers about the logic of the Crowdin workflow, so they don’t push anything to master.