How to get SQL Source Control to recognize staged/unstaged (non-committed) changes to source files?

EdgeConnex

It seems SQL Source Control only recognizes committed changes to source files in Git.  However, in Mercurial, it recognized file changes to uncommitted files seamlessly.  Made it super easy to develop via a change to source files, use SQL Source Control to Get Latest updates, and then use Visual Studio to do unit testing with updated DB objects.  But, this behavior is NOT done when using a Git repository.  Intentional?  Accidental?  Is there a way to configure SQL Source Control to do the same behavior for Git as it does for Mercurial?

DanC

Hi @EdgeConnex

I'm not familiar with how Mercurial works myself, but unfortunately, it's not possible to modify the behavior of SQL Source Control for git in this case