Comments
3 comments
-
Hi,
1- The default permissions on the local workspace don't need to be changed usually
2 - SQL Source Control does not support "git within TFS" currently, precisely due to authentication issues.
To continue using "git within TFS" with SQL Source Control you would need to use the link to a working folder option:
http://documentation.red-gate.com/displ ... ing+folder
Alternatively you can use the native TFS connection mode if you use TFVC in VSTS, or you can use the native git connection mode if you use another git hosting service (for example github).
Thank you, -
Any update on when SQL Source Control will support Git within TFS and Team Services?
More and more people are choosing this option, even Microsoft use Git internally.
You should really highlight in the product pages that Git with TFS is not currently supported, rather than people trawling through a forum to find it.
Steve -
Hi Steve,
I am sorry to say but currently we don't have an ETA on this.
Please add your support to this idea on our uservoice forum:
https://redgate.uservoice.com/forums/39 ... -under-tfs
Regarding the documentation we mention the lack of support in the *Link to Git* documentation page:
http://documentation.red-gate.com/displ ... ink+to+Git
Thank you,
Add comment
Please sign in to leave a comment.
1. When committing an SP change we receive an "Access to path [path] is denied" error during the "Sending files to source control server" stage. Yet the source control folder in question has been given relaxed security permissions (i.e. Everyone has Read/Modify/Write). If we change the file from read-only to writeable then SQL Source Control is able to commit the change to the source control folder.
2. When attempting to push the change to the remote repository using the SQL Source Control push button it correctly recognises the Team Services web address and displays an authentication dialog however, when entering the correct user credentials (username and password) it repeatedly states Access denied.