Branch Strategy and DevOps with current role limitations

Yeah, I’ve run into this same issue before. The current role setup can be a bit limiting when it comes to branching. One thing we tried was having a small group of trusted devs with elevated roles who could help manage branches for others — kind of like branch gatekeepers. Not perfect, but it helped avoid giving full admin access to everyone.

Pre-creating workspaces for each dev sounds like a nightmare to scale, especially if your team grows or changes often. Another idea might be to use automation (like pipelines or scripts) to handle branch creation based on requests — keeps things controlled but still flexible.

Curious to hear what others are doing too!

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.