1

My workspace is not reconciling after a gated check-in. I don't see an error. My files are checked in, but still showing under pending changes.

  • Doing a compare with latest shows no differences.
  • If I bypass the gated check-in, it reconciles as expected.
  • Clicking 'Reconcile Workspace' on the build menu shows a dialog that says 'No changes to reconcile'.
  • Restarting Visual Studio does not reconcile.

Our team just received new computers and everyone is having this problem. This did require us to install the latest version of Visual Studio 2019 (16.8.4). I'm not sure if it's a problem with the latest Visual studio, or the new computer.

Any advice on how to resolve this?

Daniel Mann
  • 57,011
  • 13
  • 100
  • 120
Don Chambers
  • 3,798
  • 9
  • 33
  • 74

1 Answers1

-2

The Gated check-in is used to protect against breaking changes via building the changes for validation before committing the changes to TFS. The changes actually get being committed to your TFS server only when the Gated Check-in Build is success and all configured tests are passed. Otherwise, the changes will be kept in Pending Changes.

You can reference to the following articles to try checking in Pending Changes using Gated Check-in:

Bright Ran-MSFT
  • 5,190
  • 1
  • 5
  • 12
  • Thanks for the explanation of Gated Check-ins, but that was not my question. The gated check works, the changes are committed, when I compare the file to the server version there are no differences. The problems is that the file remains under 'pending changes' as though it has not been checked in. This is new behavior after an upgrade, for several developers on my team. – Don Chambers Jan 26 '21 at 14:17
  • Hi @DonChambers, Can you try to check with the following steps: 1. Delete the workspaces and disconnect the team project. 2. Restart the Visual Studio. 3. Re-connect the team project and re-create the workspaces. – Bright Ran-MSFT Jan 27 '21 at 06:12
  • I did that, but it's no different. What's the theory behind this? As I mentioned, everyone on the team is having the problem when they get a new computer and laptop. I don't see how everyone can have a corrupted workspace. – Don Chambers Jan 27 '21 at 18:45
  • Hi @DonChambers, Does the issue occur on all the computers that has installed the latest version of Visual Studio 2019 (16.8.4)? Do you have any computer that has other versions of Visual Studio installed, such as Visual Studio 2017? Does the issue occur on the computer with VS 2017? If the issue does not occur on VS 2017, try installing the VS 2017 on the new computers to see if the issue still occurs. – Bright Ran-MSFT Jan 28 '21 at 08:05