Yep - this one is so key. You have it for git in SCA so would love to see it in SQL Source Control within SSMS.

Currently we create a branch using Jira (that's linked to Bitbucket). Then I need to go to SourceTree to fetch and checkout that branch, then switch to SSMS to do the actual work and the push. I'd love to remove SourceTree from that process.

Very useful. Right now we need to switch to SourceTree just to do this.

I would frame this as modify change management to allow GIT branch management. Currently I have to go to the command line and create and checkout a branch, then go back to CM and do my changes. I always have to remember to remove my local branch from the command line and pull master after pushing my changes to remote. Not a good experience for GIT beginners.

Also like to see branch management. At least: Create a new branch, checkout an existing branch and merge branches and push to remote. Probably want to be able to delete a local branch also.

We're just migrating across to use a 'Branch per task' driven approach.

This is the usual approach for our AppDev guys, but new to me (SQL/BI dev)

Im currently looking for a sloution to handle this very situation

Be able to create a local branch from within Source Control and even in the remote repo.

Being able to switch branches from SOC is the most common request that I get from my customers

Interested to hear more about your workflow with branching. When you're working on branches do you have multiple copies of the database, each one linked to a branch? Or do you unlink/link the same database to multiple branches depending on what you're working on?

As a workaround, we use a combination of SQL Source Control and SourceTree. SQL Source control to push changes to the (in your case) origin/test branch, and SourceTree to pull changes from the origin/master branch to the local test branch.

Ditto! I totally agree! We usually create a new copy of an existing branch, then do a pull request to merge changes back into the dev/master branches.

Additionally/Optionally -- the ability to configure the git command that is used to push/pull.

is this being considered? we also share db's and we would like the ability to push to our origin/test branch vs master. is there a work-around people are doing to push to a test branch and not touching the origin/master branch?

It would be nice to be able to create and checkout a branch form the SQL Source Control UI instead of having to switch to the VCS client.

With the recent addition of the ability to pull and push changes to/from a remote repository in Git, it would also be very useful to configure the branch to pull and push changes from or to rather than use the same branch for both purposes.

For example I may want to always pull changes from the trunk or master branch, but may want to push changes to another branch which after review may get merged manually into the trunk or master branch.

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.

Would you expect there to be some sort of branch chooser option on the commit screen? (eg a file system folder browser)

Thanks @David. My team has been pivotal in getting that moved up to where it is and we are anxiously awaiting its implementation.

Hopefully this will be addresses if/when SQL Source Control is updated with native support for Mercurial. Please go here http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/2299881-migrations-support-for-mercurial to submit a vote in favor of native Mercurial support.

My local mercurial repo is pointing to the default branch. I have database changes that I need to commit but I want them to go to a new branch. There is no way from the SQL Source Control commit window to indicate that I want to create and commit to a new branch. Currently, I have to make a bogus change in my local SQL repository directory and commit that to a named branch in order to set my location and then commit using SQL Source Control.