Where did the `Commits`, `Branches`, `Remotes`, `Stashes`, `Tags`, `Worktrees`, and `Contributors` views go in GitLens 16?

[eamodio]

Don't worry, while we've consolidated them into a single GitLens view (by default), its easy to switch back. See #3762 for more information.

[sebastian-correa]

Thanks @eamodio for this heads up, I was panicking trying to find what had gone wrong with my setup. I think the possibility of grouping things under the Git Lens dropdown is an improvement, as I can now hide stuff I don't use that often there and avoid clutter.

However, I think that having the UI change by default when updating is a bad idea, as it can have users rummaging around trying to find what used to be there and is a key part of their workflows. This is probably partly my fault because, when stuff updates, I only superficially read the myriad of popups that tend to appear because I want to get to work.

If possible, maybe having one of the popups have buttons so that the user is forced to select the new or the old UI would've prevented this issue.

[eamodio]

Sorry to cause any panic, as we certainly didn't want that, but I can certainly understand where you are coming from. We wanted to avoid having a popup for this, as we didn't want to interrupt the user's flow. And felt that the change with a one-time "welcome" view would provide both good discovery of the change and a 1-click opt-out. Had we had more control over the experience (as a VS Code extension we are quite limited in our control over the UI), we would have changed/improved things, but we wanted to ensure that existing users were exposed to the benefits of the change.

We have made some tweaks for users who haven't yet upgraded that should help with discovery a bit more -- so thank you for your feedback!

[eamodio]

Locking this issue to ensure that all further discussion happens here #3762