GitLens views don't auto-refresh if VS Code is open to a subfolder of a repository #1191
Steps to Reproduce:
Fetch in either sourceontrol -> changes -> fetch or in terminal and gitlens won't autorefresh even though the option is enabled. Tried disabling, reloading, enabling, reloading to no avail.
The "source-control" expansion panel will react to e.g. commits made from terminal, but "branches" expansion panel will not update and show the green symbol suggesting, that the branch is ahead of remote.
I also have Git: Autorefresh set to true.
The text was updated successfully, but these errors were encountered:
Can you please enable output channel logging by setting
Also is there anything else special about your repository? Symlink? Remote? etc?
I've added more logging in tomorrow's insiders edition. Can you install it from here. But be sure to disable/uninstall the stable version of GitLens first.
And then send me the logs from the start of a vscode session -- I want to look at GitLens' repository discovery logs.
@wiegell yeah, so this is what I thought:
So it looks like you are opening the
GitLens (at least in the Repositories view) will detect this and show an indicator in the UI (although its easy to miss):
And unfortunately, VS Code only supports file watching of files/folders inside the workspace/folder it was opened to. See microsoft/vscode#3025.
So unfortunately there isn't much I can do here.