CODEWITHSUNDEEP
tfs
Caleb Jares
Caleb Jares

Reputation: 6307

How do I make small local commits with TFS?

I'm in a company now that forces TFS upon us. I have used Git all my life, and I am struggling to find some features I am used to in TFS. For example, I'd like to make small commits locally and push them up later together. This way I can keep track of my changes and roll back if I ever need to. Is there a way to do this in TFS?

Upvotes: 5

Views: 879

Answers (1)

user1345223
user1345223

Reputation:

What you're looking for is called "shelvesets" within TFS.

This link explains how to create one:

To shelve folders and files from Solution Explorer

  1. In Solution Explorer, right-click, and then click Shelve Pending Changes.

  2. In the Shelve - Source Files dialog box, type the shelveset name (for example, shelvetest) in the Shelveset name box.

  3. The Shelve - Source Files dialog box includes two options:

    • Preserve pending change locally

    • By default, this option is selected. When this option is selected, the changes you made to the files or folders in your local workspace are preserved.

    • Evaluate Policies and check-in notes before shelving

    • When this option is selected, all check-in policies are evaluated before the shelveset is created. For more information, see Set and Enforce Quality Gates.

  4. In the Comment box, type Testing my shelveset, and then click Shelve.

    The files and folders are copied to the version control server and are available for other team members to unshelve.

And this link provides some background about using shelvesets:

For a variety of reasons, sometimes you need to set aside some or all of your work in progress. Shelvesets are useful when you want to stop work for:

  • Interruption: You have pending changes that are not ready for check in, but you need to work on a different task.

  • Collaboration: You have pending changes that are not ready for check in but you need to share them with another team member.

  • Code Review: You want another team member to perform a code review of your pending changes.

  • Private Build: Before you check in your changes, you can use your automated build system to build and test your code.

  • Backup: You have work in progress that you cannot finish now so you want a backup copy that is stored on your server and available to other team members who might need to access it.

  • Handoff: You have work in progress that you want to hand off to another team member.

Upvotes: 6

Related Questions