Controlling who commits code to a given database schema in Git with Azure DevOps
One of most the fun things about working as an Advocate at Redgate is getting to help clients determine their preferred workflow for database DevOps.
Teams often have unique requirements and are using different combinations of tooling, so figuring out the best way to accomplish what they need typically involves leveraging what I already know, collaborating with my coworkers and the client to generate ideas, researching and prototyping solutions, and then getting feedback from everyone.