5 results found
An error occurred while saving the commentJason Kochel commented
I don't think a branch chooser is necessary. The scenario is that, from the default branch, I'll do "hg branch NewFeature". That gives me "marked working copy as branch NewFeature". If I make a SQL change and try to commit via SSC, I'll get "branch NewFeature doesn't exist". The workaround is to commit a (non-SQL) "dummy" change to the new branch. SSC just doesn't seem to recognize the new branch until something is committed to it.
Thank you everyone for the suggestions and votes for this over the years.
I’d like to surface up a workaround for the “linking” problem which is mentioned in the comments. For the use case of easing pains around environment setup with a large number of databases, we have had customers find success using code based off Alessandro Alpi’s blog post: https://alessandroalpi.blog/2016/06/28/automatically-link-databases-to-red-gate-sql-source-control/
I do understand that this is a broader issue and hear that many of you also want command line or API support for the product in general.
If there are specific scenarios or workflows that would be useful to automate for you, this feedback is also very useful, and if you have details on the type of VCS you use and the workflow (such as a branching model) that it would fit in to, that would be very helpful for us to hear as well.