I see @smccollough created the new thread below, more specifically on the behaviour of VSTS extension 4.3.2:
Let’s follow-up there as this topic here started on VSTS extension 4.3.0, and VSTS-161 has been released in the meantime.
I see @smccollough created the new thread below, more specifically on the behaviour of VSTS extension 4.3.2:
Let’s follow-up there as this topic here started on VSTS extension 4.3.0, and VSTS-161 has been released in the meantime.