forevolve/git-extensions-for-vs-code

A VS Code extension that provides a command to browse the current project using GitExtensions, from the Explorer.

Git Extensions for VS Code

This extension provides a command to browse the current project using GitExtensions, from the Explorer and the Editor. It also support Workspaces.

Features

Explorer

From the Explorer, when you right-click (anywhere; a file or not) and then select the Browse with Git Extensions, Git Extensions will open in Browse mode for your current project.

Editor

You can right-click anywhere in an editor to Browse with Git Extensions. Git Extensions will then open in Browse mode, based on the file you are focused in.

Compatibility

The extension works with single files, folders, and workspaces.

Requirements

1. You need to have Git Extensions installed
2. Git Extensions must be available globally (for Windows users: registered in the PATH environment variable)

Git Extensions should register itself in the PATH (checkbox during the installation process). If it did not and you need to manually add a variable to your PATH, I wrote the following article about that: How to add your PHP runtime directory to your Windows 10 PATH environment variable. Just change ...\php.exe with C:\Program Files (x86)\GitExtensions\GitExtensions.exe.

Extension Settings

There are no settings at this point.

Known Issues

• The command does not work from the command palette (ctrl+shift+p). For more info, please take a look at the following issue on GitHub Also work with keyboard nav.

Release Notes

1.1.3

• Update packages
• Update README
• Update build definition
• Fix WS-2019-0310
• Fix CVE-2020-7598

1.1.1-1.1.2

• Update the vscode dependency to ^1.1.33 to remove a tar vulnerability; see CVE-2018-20834.

1.1.0

Explorer context menu

• Added support for workspace; the right-clicked context menu item is now taken into consideration, opening GitExt based on that file or directory.
• Moved the Browse with Git Extensions option up, right under the navigation section.

Editor context menu

• Added the Browse with Git Extensions command to the context menu of the editor, allowing to open GitExt from an opened file.

1.0.1

Update the vscode dependency to ^1.1.22 to remove the event-stream vulnerability.

1.0.0

The initial release of Git Extensions for VS Code, it contributes the Browse with Git Extensions command to the explorer's context menu.

git-extensions-for-vs-code's Issues

[BUG]Git push of a repository cloned with ssh does not work

How to reproduce

• Clone a repository via ssh.
• Make any change you like
• Stage changes (via git extension)
• Add commit message (via git extension)
• Try to push (always via git extension).

You will receive the following error message:

Instead via terminal

• Instead, push the same commit via the terminal, it would ask for a password related to the ssh key.
  It would be nice to ask for the password via GUI, and manage this scenario.

Also work with keyboard nav

In VSCode most commands can be invoked with autocomplete at the Ctrl-Shift-P prompt.

When you select "Browse with Git Extensions" here, however, you get an error:

Command 'Browse with Git Extensions' resulted in an error (Cannot read property 'fsPath' of undefined)

Update deprecated vscode.workspace.rootPath to workspaceFolders

• Update deprecated vscode.workspace.rootPath to vscode.workspace.workspaceFolders.
• Update tests

Update the docs

• Update the explorer context menu screenshot
• Describe the editor context menu feature description (including a screenshot)
• Add a build badge: [![Build Status](https://forevolve.visualstudio.com/git-extensions-for-vs-code/_apis/build/status/GitHub%20Deployment%20Pipeline)](https://forevolve.visualstudio.com/git-extensions-for-vs-code/_build/latest?definitionId=35)
• Add the badge to package.json; see Extension Manifest File - package.json for the file format.

Write some unit tests

• Write some unit tests
• Run those tests during the build
• Create a light build that only build and test the extension, no publish (or split the current build into build/release).
• Enforce that the build succeeds before allowing PR merge

Add support for workspace

When a user right-click > Browse with Git Extensions in a workspace, the script should open the clicked repository instead of the first folder in that workspace. Replace vscode.workspace.rootPath by something that finds the right directory.

Find a better file detection "algo"

See the TODO in BrowseCommand.trimPathToDirectory()