In Toad 12.12 and earlier, all clone, pull and push operations need to be managed outside of Toad for Oracle. Toad for Oracle 13.0 will support clone, pull and push operations from inside Toad for Git and Mercurial. Support has been added for the next beta.
As far as VSTS is concerned, there are a few things to consider:
-
The Visual Studio Team Services client in Toad is designed for TFVC repositories only. The REST API’s are very different for Git repositories stored in Visual Studio Team Services than they are for TFVC.
-
You will need to configure “Alternate Credentials” for your Visual Studio account in order to access your repository.
-
Forcing revisions in Toad is not currently supported by VSTS. Attempting to do so will return an error from VSTS.
-
You will have access to work item tracking when using the Visual Studio Team Services client.
For VSTS-hosted Git repositories: -
You should be able to use the Git client within Toad for Oracle and simply clone from the VSTS server.
-
You will need to configure “Alternate Credentials” or “Personal Access Tokens” for your VSTS account in order to pull/push to your repository
-
You should enable Git’s credential manager to securely handle your username and password or personal access token when performing pull/push operations
-
Forcing revisions in Toad is not supported by Git. Git has no ability to force a revision of unchanged code.
-
You won’t have access to work item tracking when using Git within VSTS.
I hope this helps answer your question. Please feel free to let me know if you have any others.
Thanks,
-John