Using the Check In and Pending Changes Windows

Team Foundation source control files are checked in to the source control server by using the Pending Changes window or the Check In dialog box. The Check In dialog box is opened from either the Source Control Explorer or the Solution Explorer. These check-ins are submitted as changesets.

Note

You can also perform a check in from the command line. For more information, see Checkin Command.

Using the Check In or Pending Changes Window, you can accomplish the following tasks:

• View all the pending changes associated with your workspace.

• Check in some or all the pending changes in your workspace to the source control server. For more information, see How to: Check In Pending Changes. When you check in pending changes, Team Foundation creates a new changeset in the server. Thereafter, your teammates can access your code by performing a Get Latest operation. For more information, see How to: Get the Source for your Team Project.

  Tip

  Use the Get Latest command before checking in your Pending Changes to download the most recent sources from the server and compile your code to make sure that it does not break the build.

• Associate or resolve work items with the changeset during the check-in process. For more information, see How to: Check In Pending Changes and How to: Associate Work Items with Changesets.

• Provide check in notes to be associated with the changeset. For more information, see How to: Check In Pending Changes and How to: Associate Check-in Notes with Changesets.

  Note

  Check-in notes can be configured by an administrator. For more information, see Working with Check-in Policies and Notes.

• Review check-in policy adherence for the changes. These policies are configured by an administrator and if necessary, the policies can be overridden. For more information, see How to: Check In Pending Changes and How to: Override a Check-in Policy.

  Note

  Check-in policies can be configured by an administrator. For more information, see Working with Check-in Policies and Notes.

• Send e-mail notifications to team members who have subscribed to be notified when check-ins occur. For more information, see Setting Alerts.

• Undo pending changes to revert the changes on your local system back to the base workspace version, which is prior to any changes.

• When necessary, you can move pending changes out of your workspace using the Shelve command. Shelving enables you to set aside a batch of pending changes temporarily and optionally remove the pending changes from your workspace. For more information, see Working with Source Control Shelvesets.

See Also

Reference

Checkin Command

Concepts

Submitting Changes to the Source Control Server
Pending Changes
Working with Source Control Workspaces
Working with Source Control Changesets
Working with Source Control Shelvesets