Source Control + Git Questions

[SimonT]

Hi, I have been struggling to get Source Control within dbForge Studio for SQL Studio to work with my git repository.

1. Unable to use SSH for authentication. Setting the URL to ssh://user@host:path.git brings up the SSH settings, however I receive "Exception caught during execution of ls-remote command URI is not supported: ssh://user@host:path.git"
2. Tried using an existing clone, however it doesn't appear to like my clones that are setup with private keys (SSH)
3. I created a Github "Personal Access Token" to bypass the 2FA/Private Key limitation. It appeared to work and cloned my repo, but failed due to the file path exceeding 248 chars. I changed dbForge's repo location and it cloned my repository, but during the link stage, it fails saying "Checkout conflict with files: <list of files>", the repo is emptied and all that remains is a partial .git folder.
4. I am unclear as to how Source Control wants to use a Git repository. Does it use a sub-folder? Does it expect a dedicated repository?

The only method that has worked for me so far is to use a Working Folder, but that isn't as feature rich as the proper SCM links as there is no history without manually checking out past revisions.

[alexa]

SSH connections are supported in another our product dbForge Studio for MySQL https://www.devart.com/dbforge/mysql/st ... nload.html

Please also see the 'Creating SSH Connection' demo video https://www.devart.com/dbforge/mysql/st ... -more.html

[SimonT]

Hi Alexa,

The linked video did not help. I'm looking to use SSH as a means to connect to my Git repository for Source Control, not as a means to connect to my SQL Server database.

The most information I have found so far is here: https://www.devart.com/dbforge/sql/sour ... index.html but it isn't enough to help.

Simon

[alexa]

Thank you for the reply.

We will investigate this issue and will answer you as soon as possible.

[alexa]

Unable to use SSH for authentication. Setting the URL to ssh://user@host:path.git brings up the SSH settings, however I receive "Exception caught during execution of ls-remote command URI is not supported: ssh://user@host:path.git"

Here is the supported format of URL for SSH:
ssh://<user><host>/<path[.git]>@

Tried using an existing clone, however it doesn't appear to like my clones that are setup with private keys (SSH)

Could you please describe how you came to such a conclusion?

I created a Github "Personal Access Token" to bypass the 2FA/Private Key limitation. It appeared to work and cloned my repo, but failed due to the file path exceeding 248 chars. I changed dbForge's repo location and it cloned my repository, but during the link stage, it fails saying "Checkout conflict with files: <list of files>", the repo is emptied and all that remains is a partial .git folder.

We were not able to reproduce this issue. You can try unlinking the database and create a new link.

I am unclear as to how Source Control wants to use a Git repository. Does it use a sub-folder? Does it expect a dedicated repository?

That's right, it's a dedicated repository at the moment. In future, we may implement support for sub-folders.

[SimonT]

Here is the supported format of URL for SSH:
ssh://<user><host>/<path[.git]>@

I did get this to work. The URL I was using had a : separating the host and path instead of a /. I believe your URI format has the @ in the wrong spot, it should be:
ssh://<user>@<host>/<path[.git]>

Tried using an existing clone, however it doesn't appear to like my clones that are setup with private keys (SSH)

Could you please describe how you came to such a conclusion?

On the "Source Control Repository Properties" window, when linking a database, i selected Git, then "Use existing local clone" and put in the path to an existing clone on my PC. The window properly populates the "Remote repository", however the "Security settings" is set to None and it says "Using insecure connection". Clicking "Test" says the connection works. I am able to complete the Database Linking process, however when the Source Control tab opens up for that database, it fails to refresh the repository status and shows "Unsupported credential item" in the Error List. This may be related with the previous item.

I created a Github "Personal Access Token" to bypass the 2FA/Private Key limitation. It appeared to work and cloned my repo, but failed due to the file path exceeding 248 chars. I changed dbForge's repo location and it cloned my repository, but during the link stage, it fails saying "Checkout conflict with files: <list of files>", the repo is emptied and all that remains is a partial .git folder.

We were not able to reproduce this issue. You can try unlinking the database and create a new link.

I can if you'd like, but this error is likely a result of me trying to use the Git integration with an existing repository with other code in it and not as a sub-directory. I have opted not to use the Git integration and have opted to use a Working Folder within my Git repo instead (see below).

I am unclear as to how Source Control wants to use a Git repository. Does it use a sub-folder? Does it expect a dedicated repository?

That's right, it's a dedicated repository at the moment. In future, we may implement support for sub-folders.[/quote]
That's unfortunate, but ok. I will use the "Working Folder" setup until then. It appears to be working as expected.

[alexa]

Thank you for the reply.

We replied to you by e-mail.