Hi everyone,
is there any best practice to manage multiple branches of an SQL server database project.
Sample scenario:
1. There is a main branch
2. Developer A creates a branch A
3. Developer B creates a branch B
4. Developer A creates a pull request and merge let's say a new table into main.
5. Developer B creates a pull request containing another new table.
The problem by the second pull request is the project file. File for different sql objects are not getting in conflict since every new table gets a dedicated file in the correspondent schema folder. From the other side the project file in Main points to the table created by user A but does not contain the table in the pull request and viceversa.
Until now we are overcoming this drawback merging the project file manually but I want to double check if there is a better way to proceed.
Any help will be appreciated.
Best regards,
Paul


