Skip to main content

Troubleshooting

I get an error when...#

When experiencing an error please check:

  1. That you have the latest version of your IDE installed, by going to 'Help > Check for Updates...' in the IDE menu.
  2. That you have the latest version of the extension installed by restarting your IDE. You will be prompted to download the latest extension if a new one is available.

If both your IDE and the extension are up to date, please review the list below for solutions to common issues. If you do not find your issue or the recommended solution does not work, please contact developer support.

I make changes to a script or config but the option to commit the file isn't available#

Sometimes you may find that after making a change to a script or user config, that the icon for the file in the extension tree doesn't update to indicate that the file was modified. This can happen when your local workspace becomes out of sync with the latest committed version on .

There are a couple ways you can handle this situation.

Before continuing it is important that you first run 'Diff with Local' on the script or config you wish to commit. This will show you your changes compared with the latest version on . Be sure to carefully merge any changes your edits do not include.

Force Commit Your Changes#

  1. Enable the Force Commit command in the extension settings
  2. Right click the script or config you wish to commit and click 'Force Commit to New Version'

This will commit your changes to a new version of the script or config bypassing all commit protections.

Reset Your Local Extension Workspace#

You can also reset your local extension workspace. The safest way to do so is to:

  1. Save all open scripts and configs
  2. Right click on the script which you have open and which will not commit, and click on 'Reveal in File Explorer'
  3. Navigate up a couple folders to a folder whose name includes
  4. Rename that folder to .backup
  5. Close and reopen VS Code
  6. In the extension tree, open the script or config once again. It should open with the content last committed successfully
  7. Open the script off disk from your .backup directory
  8. Copy and paste your changes into the script

Following these steps should result in the extension recognizing your changes and enabling the capability to commit.