Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PSA : How to make sure the extension works (VS Code's SCM issue) #343

Open
EDM115 opened this issue Oct 8, 2024 · 0 comments
Open

PSA : How to make sure the extension works (VS Code's SCM issue) #343

EDM115 opened this issue Oct 8, 2024 · 0 comments

Comments

@EDM115
Copy link

EDM115 commented Oct 8, 2024

vscord may rely on vscode.git to be started before being able to start in the first place (probably if you configured it to react to being in a git repo to show the url on buttons).
If you're someone who have a ton of extensions installed (and a potato pc), loading all of them will take a while and they might not load up in the order you want.
a while back I suggested to load the extension only after VS Code's git, and this was added then reverted.

So far the only fix around this (so I don't get the messages seen in #318 #297 and others) was to open the Source Control view as soon as VS Code starts. This way it prioritize loading vscode.git and this kinda makes sure that it is loaded before vscord.

If you want to automate it :
Do F1 -> Tasks: Open User Tasks
Paste the following :

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Open SCM View on startup",
      "hide": true,
      "command": "${command:workbench.view.scm}",
      "runOptions": {
        "runOn": "folderOpen"
      }
    }
  ]
}

Now, everytime you open VS Code/open a new folder in it it will (in some time, not instantly) switch to the Source Control view, ensuring vscord will always be loaded :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant