Converting remote url from ssh to https

[dral3x]

Hi there,
I started using this extension recently, and while useful for a specific repository, I found out it was breaking the repository configuration for most of my projects.

The reason is the conversion of the SSH-based remote URL into HTTPS-based.
Looking at the code, I don't see a way to disable this behavior.
Can you help me understand why it's doing this? And how to prevent/enable this on specific repositories only?

Thank you!

[incompletebiped]

Hi! I ran into the same issue and wanted to share what worked for me.

You're right that GitShift converts SSH remotes to HTTPS — and if you're using SSH keys for auth, that breaks everything. The root cause is that GitShift authenticates via OAuth/PAT over HTTPS, so it needs HTTPS remotes to function. SSH keys and GitShift's credential system are incompatible.

My workaround:

1. Convert affected repos to HTTPS remotes:

   git remote set-url origin https://github.com/OWNER/REPO.git
   

2. Use GitShift's Add/Replace Token option with a Personal Access Token (PAT) instead of OAuth — this is more reliable, especially in Cursor.

3. Configure Git Credential Manager to store credentials per repo path rather than per host (important if you have multiple GitHub accounts):

   git config --global credential.github.com.useHttpPath true
   

The trade-off is you can no longer use SSH for those repos, but once everything is on HTTPS + PATs, GitShift works great. The first push to each repo will prompt for credentials once, then it's silent going forward.

Hope that helps — would be great if the extension had an opt-out for the SSH conversion behavior for people who prefer to stay on SSH!

[dral3x]

Thanks @killianconsulting for sharing your workaround.

Now I understand why GitShift needs https; it makes sense. The scary part is that it automatically converts ANY repo you open on Visual Studio, which was unexpected for me. I would appreciate a confirmation alert like "hey mate, I need to adjust this repo git configuration to make it work properly with GitShift. Are you ok with that?"

I use VS for editing many projects on many repositories, and only a subset of them require the usage of GitShift for me.
At the end, I switched back all repositories and split the tool I use (command line for the majority of repos, github desktop for those special ones). It fits my workflow better.

That being said, this tool is great! Just a bit too aggressive on a delicate configuration.