Comments
Sort by recent activity
Just in case anyone runs into the same thing, I deleted the original folder and started over. I didn't bother trying to connect to GitLab because I already know the SSH key/passphrase isn't supported. I'm just connecting to the working folder and so far everything is working. / comments
Just in case anyone runs into the same thing, I deleted the original folder and started over. I didn't bother trying to connect to GitLab because I already know the SSH key/passphrase isn't support...
I just unlinked the db and now that I'm trying to link again I get the message: "That repository has staged changes. You need to commit, stash, or unstage the changes before linking." I'm guessing that is because my attempted commit completed half-way. Is there a way I can start over? This is just adventureworks, so I don't care about this particular db. / comments
I just unlinked the db and now that I'm trying to link again I get the message: "That repository has staged changes. You need to commit, stash, or unstage the changes before linking." I'm guessing ...
Yes, the issue appears when I try to commit the changes to the local working folder. I'll try to unlink/relink, hopefully that will do the trick. / comments
Yes, the issue appears when I try to commit the changes to the local working folder. I'll try to unlink/relink, hopefully that will do the trick.
Yes, I'm using a passphrase. I know that SQL Source Control can't sync with the remote repo using SSH/passphrase. When I tested last year, I had it all working by saving to the local folder from within SSMS and then using git bash to push/pull to the remote location. The permission problem appears now when source control wants to overwrite files in my local folder. / comments
Yes, I'm using a passphrase. I know that SQL Source Control can't sync with the remote repo using SSH/passphrase. When I tested last year, I had it all working by saving to the local folder from wi...