In the Changesets view, have a split view, that shows the filenames of the files in that change set.

The view could be just like you use in the Pending Changes view, where the split is resizable, with the top half showing change sets, and the bottom showing the files in the changeset currently selected. That way you can quickly arrow up/down through the change sets and see the files instantly in that set.

If you want to get to the diffing tool, you still need to double click the changeset. This is only about showing the files in the changeset.

Some configuration files & libraries etc. can need to be present, but customized/recompiled per-developer.

We want to commit them to the repository (as they DO need to be present in at least a "default" state), but then once downloaded, we want developers to not have to worry about committing them ever. This feels like a very reasonable and common use case, and one for which "hidden_changes.conf" is made for.

However, when we switch branches/changelist (which is very often!), we get the following error-looking dialog for any files we are locally changing but that ARE in "hidden_changes.conf" (see image).

Ideally, if a file is in "hidden_changes" it wouldn't cause such an error and not put up any dialog. (e.g. I know it's a different use case but files that are cloaked don't put up a dialog) If there are any concerns about communication at the very least it should be a more friendly dialog such as "the following files are marked as HIDDEN CHANGES and have been changed and will NOT be updated to the new change list".

Currently, with "Move Changeset" I can only move to a new branch or an empty one.

But often I find myself quickly fixing a small bug or tweak a value, and switching to a different branch is something I don't think about at that moment. But the changeset does not belong on the branch that I committed it to.

It would save an incredible amount of time if "Move Changeset" would do the following, when selecting a non empty branch:
- Cherry Pick the full changeset from the target branch, including the comment
- Delete the changeset in question

Now I understand that deleting a changeset anywhere on a branch creates a sort of "Tower of Hanoi" challenge, of having to shelve all the commits on top of it, delete the changeset in question, and stack them back on. For now it would already be useful if I could do this with the latest changeset (no further dependencies).
But being able to delete changesets with dependencies (instead of messy reverse commits) would be very useful in it's own right.

I often need to look up the history of a file, but I only care about its changes on the /main branch. From the regular history view, when the file got changed on a branch, it is unclear whether that branch made it back to /main or not. The current history view is fairly pointless because there is no way to tell which changes are relevant and which ones have been abandoned.

The 2D history view on the other hand is way too cluttered and cumbersome to navigate for any non-trivial project. Especially as it includes changesets where the file was merge from /main to another branch, which is exactly the opposite of what I want to know.

What I really want is a way to filter the regular history view to a single branch, but show all changeset affecting the file, including merges. The table format is good, I just need a way to filter out all the irrelevant changes that never made it back to /main.

Searching in Visual Studio allows me to set multiple search terms separated by a space in order to better narrow my results. This is helpful if you aren't sure if the name of the file is "ProjectXMLData" or "ProjectDataXML", but you know for sure it has Project and XML in the name.

Attached Images
- VSSearch01 - Shows searching for all 'project'
- VSSearch02 - Shows adding 'xml', but not as an exact match. The results are still displayed as expected
- WSSearch01 - Shows searching for 'project' and results show as expected
- WSSearch02 - Shows adding 'xml', but no results are returned

When trying to switch the workspace to a different changeset/branch, the user is first asked if he's sure, but then gets an error if there are pending changes.

It would be great if the question dialog would show how many pending changes there are (and maybe a tooltip with a list of all changed files?). Then, if the user decides to go through with it anyway, the pending changes should be reverted (maybe have a checkbox, so the user is really sure) and the switch should be performed.

When there are no pending charges, the switch should just happen without asking.

I often have loose files that got changes by the IDE or Unity that I can safely discard. Having to do this manually every time can be quite annoying when quickly zapping through different changesets.