Export (0) Print
Expand All
0 out of 1 rated this helpful - Rate this topic

Submitting Changes to the Source Control Server

Team Foundation source control files are checked in to the source control server using the Pending Changes window or the Checkin dialog box. For more information, see Using the Check In and Pending Changes Windows. These check-ins are submitted atomically as changesets. During a check-in the user can associate work items, provide release notes and review check-in policy adherence for the changes. Various information of the check-in process can be customized by an administrator.

The Team Foundation source control check in process performs the following actions:

  • Validates compliance with check-in policy.

  • Submits source file changes.

  • Updates associated work items.

  • Sends e-mail notification.

How the check in process works

When the check-in operation is performed, the source file updates either succeed completely or fail completely. If any of the changes in the list of pending changes cannot be submitted to the server (for example, you lose network connectivity in the middle of the operation), none of the changes are committed and a changeset is not created.

If the basis version of any item in the list of pending changes differs from the latest server version (for example, you checked out version 4 of stellar.cs and the latest server version is now version 6), Team Foundation prompts you to resolve any conflicts between your version and the latest server version first. The Resolve dialog box appears to help you investigate and resolve version differences. After you resolve outstanding differences and re-test your code, you can then attempt to check in your changes again.

Upon completion of the check-in operation:

  • The changes are committed to the server as a changesets and the changeset number is displayed.

  • Files that were checked out are returned to a read-only state. Your changes appear in the server and can be retrieved by other users.

  • E-mail is delivered to team members who have subscribed for check-in notification.

  • Work items are updated.

Customizing the check in process

A Team Foundation administrator can configure the check-in notes and check-in policies that apply to a given team project. For more information, see Walkthrough: Customizing Check-in Policies and Notes.

In This Section

Using the Check In and Pending Changes Windows

Overview of the Pending Changes window.

Pending Changes

Describes locally-persisted changes in source control.

How to: Check In Pending Changes

Describes the procedure used to check in pending source control changes with the Pending Changes window.

How to: Associate Work Items with Changesets

Explains the steps required to associate work items with a changeset.

How to: View Work Item Details from Pending Changes Window

Describes the steps used to view work item details from the check in and Pending Changes window from the work item channel.

How to: Associate Check-in Notes with Changesets

Explains the steps required to associate release notes with a changeset.

How to: Override a Check-in Policy

Describes the steps taken to override a check-in policy.

How to: Roll Back a Changeset

Describes how to overwrite a server file.

Reference

Related Sections

Working with Source Control Files and Folders

Provides information on basic source control functionality such as checking in and out files, adding, renaming, moving and deleting files and folders, and working with shelvesets.

Adding Projects and Solutions to Source Control

Provides information on adding projects and solutions to Team Foundation source control.

Team Foundation Source Control Walkthroughs

Lists walkthroughs which explore using source control, customizing a source control check in and using source control from the command line.

See Also

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.