My team is currently using gitflow workflow into develop branch.
Here is an overview for what we are doing. We are a sql server data warehouse team using Azure repos and Azure devops to build and deploy our code to SSIS, SSAS, and 30+ databases in our environment. I typically deploy to a integration server and then to a prod server. I have an auto build for our SQL server solution that triggers on checkin to the develop branch. I run manually a build that generate the deployment scripts. All the SSAS and SSIS builds and deployments are triggered on the checkin to the branch.
I am looking at trying to migrate to a workflow that would be a pull request so I don't have a broken build that holds everyone eases deployments. If someone breaks the build in the develop branch then I cannot deploy by the current method.
Prior to moving to the azure devops I was using a release workflow to create the deployment artifacts manually and I would deploy everything manually. This was a completely manual process and time consuming process that was very tedious.
I would like to figure out a path to get to using pull request. Does this mean I would do away with gitflow process? My team is currently using VSCode for creating features and this part works well. I am looking for advice for moving forward with pull request.