Allow other SCM setups for VSCode (remove git SCM requirement)

[jonnyboynewton]

Validations

• [ ] I believe this is a way to improve. I'll try to join the Continue Discord for questions
• [ ] I'm not able to find an open issue that requests the same enhancement

Problem

The VSCode plugin doesn't function in a workspace that doesn't have git (so for a perforce client-based workspace, for example). I get the following error:

Why does it need the git SCM plugin? What is it doing that it would need that?

Solution

Allow the workspace to have other than the git SCM extension active.

[jpaveg]

I just got this error after updating to v0.9.122, and I do have the git extension running in my workspace.

[sestinj]

@jpaveg @jonnyboynewton I've removed this dependency in the latest pre-release, so this should be resolved. Let me know if for some reason you're still having problems.

We use git to manage indexing between branches, but this should still work fine in a perforce workspace. I added the dependency explicitly so that it could force the git extension to load prior to Continue, but it turned out that this had unintended side-effects/didn't work as I expected

[jonnyboynewton]

@jpaveg @jonnyboynewton I've removed this dependency in the latest pre-release, so this should be resolved. Let me know if for some reason you're still having problems.

Excellent! Thanks!

We use git to manage indexing between branches, but this should still work fine in a perforce workspace. I added the dependency explicitly so that it could force the git extension to load prior to Continue, but it turned out that this had unintended side-effects/didn't work as I expected

is this 0.9.123? or do I need to wait for 124?

[jonnyboynewton]

nvm - i see 124 available now