How to avoid TFS Code Reviews dominating my shelveset list
When using the Request Review feature in VS/TFS a shelveset is created with the proposed changes. This shelveset stays around when the review finishes, both if it is accepted and if it is rejected.
This is all fine but the review shelveset tends to dominate my list of shelvesets making it difficult to find a 'real' shelveset. Deleting the shelveset after the review has finished, seems to be bad as it is linked to the review which is linked to the final changeset.
So my question is whether there are a way of hiding these review shelvesets?
We are using Visual Studio and TFS 2015 Update 3. Here is how it looks:
There is no way of hiding these review shelvesets, unless delete them. However,
if you have deleted the corresponding CodeReview_XXXX shelveset as part of clean up activity at a later date.
Then, users go back to the same code review for some investigation, Code Review details doesn't get displayed.
If you need this feature, suggest you to add a related uservoice or vote up for below idea, this is pretty much the same thing...
TFS: Code Reviews: Shelveset based: Unable to view any details of a code review if one happens to delete corresponding code review shelveset
- Visual Studio / Nuget puts files in the wrong place
- CodeLens not showing references
- TFS 2017 Git API - Get Tag By Name
- How to branch my Visual Studio Online (TFS) Solution?
- No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again
- WorkItem Creation Transaction Rollback
- Opening Source Control Explorer in Visual Studio 2022
- Remove project from visual studio solution
- Folders created in visual studio solution under solution explorer not appearing in source control explorer
- How to force Visual Studio to use the TFS source control provider and not GIT provider
- Error 500 while creating Azure DevOps server connector in Microsoft teams
- Get Visual Studio to run a T4 Template on every build
- How to Retrieve the Triggering Pipeline's runName in a YAML Release Pipeline
- 401 - Unauthorized: Access is denied due to invalid credentials when Trying to access the TFS API by postamn
- How to get a branch name for a dedicated changeset number via PowerShell
- TFS build write message to summary
- Exception setting "CursorPosition": "The handle is invalid." when running pipeline task using PowerShell Core
- Azure DevOps. Can't trigger a pipeline in Repo A when a commit is done in repo B
- TFS and referenced DLLs
- How to Migrate TFVS project to Azure Git Repos from different Organization
- TFS source control - new files not automatically detected as pending changes
- Azure DevOps API Authentication
- How can we make a Work Item Creator automatically a Follower?
- Task could not find "LC.exe" using SdkToolsPath
- How do I move and rename a project in both TFS & VS2012
- Renaming the containing project folder in VS.NET under TFS
- How to Filter Links Using <LinksControlOptions> with Link Comment Value in Azure DevOps Process XML?
- Commit all is greyed out in Team Explorer in VS 2015
- Merge TFS changeset between branches rather than selecting files
- Find and remove duplicate entries in csproj file