Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
Visual Studio 2019 | Visual Studio 2022
A Team Foundation Version Control (TFVC) changeset is a permanent part of the history of your version-controlled items and can't be undone or removed. However, you can roll back the effects of one or more changesets.
You can also use the tf
command-line utility to roll back changes. For more information, see Rollback command (Team Foundation Version Control).
Category | Requirements |
---|---|
Permissions | Member of the Contributors group for your project. |
For more information, see Default TFVC permissions.
For example, a developer wants to remove the effects of a changeset:
In Visual Studio Source Control Explorer, right-click an item and choose Rollback.
Note
The item you select determines the scope that the rollback changes.
In the Rollback dialog box, select Rollback changes from a single changeset.
Specify the changeset, and then select Rollback.
For example, a developer wants to remove the effects of some consecutive changesets:
From the History window, select two or more consecutive versions, right-click, and choose Rollback.
Or, in Source Control Explorer, right-click an item and choose Rollback.
Note
The item you select determines the scope that the rollback changes.
In the Rollback dialog box, select Rollback changes from a range of changesets.
Specify the changeset range, and then select Rollback.
For example, a developer wants to roll back a file to an earlier version, eliminating the effect of all changesets that occurred after that version:
In Source Control Explorer, right-click an item and choose Rollback.
In the Rollback dialog box, select Rollback to a specific version.
Specify the version details, and then select Rollback.
If your change is still pending, that is you haven't checked it in, you can undo the change instead of rolling it back. See Develop code and manage pending changes.
Like most changes you make to files, a rollback change is queued as a pending change. After you roll back the files, you can view the files you're changing and compare the files with the latest version on the server. After you confirm that the changes match what you intend to do, you can check in your changes.
Rollback doesn't delete changesets or any data. If you change your mind, use rollback to revert the content of the files back to their state before the rollback.
Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowTraining
Module
Manage changes to your Bicep code by using Git - Training
Learn how to use Git version control with your Bicep files and infrastructure as code.