Change:
const disposableStore = new DisposableStore(); disposableStore.add(resourceGroup.onDidChange(() => this.updateChildren(repository))); <del> disposableStore.add(resourceGroup.onDidChangeResources(() => { this.updateChildren(repository); this.onDidActiveEditorChange(); })); </del> <ins> disposableStore.add(resourceGroup.onDidChangeResources(() => this.updateChildren(repository))); </ins> resourceGroupDisposables.set(resourceGroup, disposableStore); } }

Discussion:
Type: <bBug</banytime i stage changes, the staged changes block of the SCM is collapsed and requires me to manually expand it. previously it would be expanded. VS Code version: Code - Insiders 1.85.0-insider (, 2023-11-14T05:45:03.848Z) OS version: Darwin arm64 23.2.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (20)</summaryExtensionVersion ------ vscode-base640.1.0 inline-hasher1.1.0 spellright3.0.118 iam-policy0.0.1 copilot1.136.0 copilot-chat0.10.1 terraform2.29. vscode-kubernetes-tools1.3.15 indent-rainbow8.3.1 ytt-lint0.3.1 vscode-yaml1.14.0 vscode-gitweblinks2.9.3 iam-legend1.1.48 kubernator-vscode1.0.0 code-spell-checker3.0.1 shellcheck0.34.0 sort-lines1.11.0 errorlens3.15.0 vscode-icons12.6.0 json2.0.2 (1 theme extensions excluded) </details<!-- generated by issue reporter --
I'm having the opposite problem... No matter the value, whenever I stage a file - it automatically expands "Staged Changes". So I have to collapse it again or scroll a lot to see unstaged changes. I think something got broken there...
sorry for not getting back to you on this until now. This milestone we have done a large refactoring of the Source Control tree view and it looks like this might be a regression that was introduced as part of that refactoring. I believe I have tracked it down, so I am pushing a fix to this.
This still doesn't seem to be working correctly, and I don't see any difference when changing the value of . to false a change, collapse that group in the SCM view tabs to a file that has a staged change result: Staged Changes group expands Also, staging a change doesn't expand that group if it was collapsed and : true. I wouldn't necessarily expect that, but it sounds like that was the original issue?

Setting to is a workaround Also on fix PR page it says "This PR’s merge commit doesn’t appear in any tags" so maybe it wasn't released yet?
Not sure if related, but also started seeing this: ! And overall weirdness navigating. For example when I click on file in explorer view - nothing happens, it doesn't open. Window reload fixes. And when renaming file, it looses the name in the UI shows up as blank. Again window reload fixes. And number of files on the right doesn't reload... !
that is unrelated to this issue. We are spinning a new Insiders build to get that fixed.
thank you very much for verifying this issue. The setting is not in scope for the issue that was reported here. That setting only controls whether the "Staged Changes" group is being shown when empty or not. Here are the verification steps: Open a folder/workspace that contains a git repository Ensure that is set to Make changes to 2/3 files, and save the changes Confirm that the files appear in the "Changes" resource group Stage the first file Confirm that the file is moved to the "Staged Changes" resource group Confirm that the "Staged Changes" resource group is expanded Collapse the "Staged Changes" resource group Stage another file Confirm that the "Staged Changes" resource group stays collapsed