Git: Symlink support
See original GitHub issue- VSCode Version: 1.0.0 (1.0.0)
- OS Version: OSX 10.11.4 (15E65)
Steps to Reproduce:
- Create a new project with git repository initialised.
- Create a folder /foo/bar
- Add a symlink from /foo/bar to /bar
ln -s /foo/bar .
- Go to Git tab on vscode, and stage
/bar
folder.
If now you click on staged /bar
folder, you’ll get an error Warn: Can't open this git resource.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:174
- Comments:50 (4 by maintainers)
Top Results From Across the Web
How does Git handle symbolic links?
So a symbolic link is one more file, just as a README.md or a Makefile . Git just stores the contents of the...
Read more >Symbolic links in Git
Here's how to track symbolic liks in a Git repository, in a way suitable for ... Git can track symlinks as well as...
Read more >Git - git-symbolic-ref Documentation
git /HEAD was a symbolic link pointing at refs/heads/master . When we wanted to switch to another branch, we did ln -sf refs/heads/newbranch...
Read more >Symlinks in Git - Personal Programming Notes
How Git deals with symlinks is defined in the git config core.symlinks . If false, symbolic links are checked out as small plain...
Read more >Symbolic link does not work in Git over Windows
I'm specifically talking about symlinks inside a Git repository. They are not portable. A link inside the repository pointing to a file outside ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
this is the most annoying bug i’ve ever encountered yet still not fixed after 5 years. Hope it will be fixed soon
I’m adding another $300 bounty to this issue; as mind-boggling as it is to see it still be a problem 5 years later, we’re still losing productivity to the crashes and long delays associated with the occasional use of SSHFS for remote editing.