We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
hello, i have a problem installing go outline in vs code. Installing 1 tool at C:\Go\bin\gocode\test\bin go-outline
Installing github.com/ramya-rao-a/go-outline FAILED
1 tools failed to install.
go-outline: Error: Command failed: C:\Go\bin\go.exe get -u -v github.com/ramya-rao-a/go-outline
exit status 1github.com/ramya-rao-a/go-outline (download)
fatal: not a git repository (or any of the parent directories): .git package github.com/ramya-rao-a/go-outline: exit status 128
The text was updated successfully, but these errors were encountered:
No branches or pull requests
hello, i have a problem installing go outline in vs code.
Installing 1 tool at C:\Go\bin\gocode\test\bin
go-outline
Installing github.com/ramya-rao-a/go-outline FAILED
1 tools failed to install.
go-outline:
Error: Command failed: C:\Go\bin\go.exe get -u -v github.com/ramya-rao-a/go-outline
cd C:\Go\bin\gocode\test\src\github.com\ramya-rao-a\go-outline; git config remote.origin.url
exit status 1github.com/ramya-rao-a/go-outline (download)
cd C:\Go\bin\gocode\test\src\github.com\ramya-rao-a\go-outline; git pull --ff-only
fatal: not a git repository (or any of the parent directories): .git
package github.com/ramya-rao-a/go-outline: exit status 128
cd C:\Go\bin\gocode\test\src\github.com\ramya-rao-a\go-outline; git config remote.origin.url
exit status 1github.com/ramya-rao-a/go-outline (download)
cd C:\Go\bin\gocode\test\src\github.com\ramya-rao-a\go-outline; git pull --ff-only
fatal: not a git repository (or any of the parent directories): .git
package github.com/ramya-rao-a/go-outline: exit status 128
The text was updated successfully, but these errors were encountered: