Check in Your Work (Team Explorer Everywhere)
Use the Pending Changes page to check in your code to the team’s codebase.
You must be one of the Contributors for your team project. See Team Foundation Server default groups, permissions, and roles.
What do you want to do?
You can specify which file changes you want to check in. On the Pending Changes page, select one or more changes in the Excluded Changes section. Choose Include from the shortcut menu. You can also scope your check-in as you work in other areas of Eclipse:
In Package Explorer or Project Explorer, select one of the following:
One or more of the code projects
One or more folders
One or more files
After you select the items, open their shortcut menu, and choose Team, Check In Pending Changes.
In Source Control Explorer, select one or more items with pending changes or one or more folders that contain items with pending changes. (Items with pending changes are indicated by this symbol: ). Open the shortcut menu of the selected items, and choose Check In.
When you change files in your codebase, you typically do so to complete a task, fix a bug, or satisfy the demand of some other kind of work item. When you check in the changes, you should associate such work items with the changes you are checking in. Benefits of doing so include:
A team member who looks at the work item can link directly to the changeset to see the work that you did.
A team member who reviews the history of a file you changed can view the changeset and see the work items that were the justification for the change.
If you build your changes in your automated build system, your team members can see in which completed build the task was completed or the bug was fixed.
To associate work items with your check-in:
Choose the Add Work Item by ID link in the Related Work Items section.
Choose a query from the Queries drop-down list in the Related Work Items section. In the Work Item Query Results editor, use the shortcut menu of a work item to associate it with a changeset.
Next to each work item, select how it should be related to your check-in: Associate or Resolve (available only if the work item is not already in a state that precludes this relationship, such as Resolved, Done, or Closed).
You can open the shortcut menu of an associated work item and then choose:
To check in your changes
In Team Explorer, choose Home, and then choose Pending Changes.
On the Pending Changes page, enter a Comment so that teammates who later need to review and understand the history of your files will understand what you did.
Some teams prefer (and in some cases implement a check-in policy to require) their members to provide certain kinds of information about each check-in. If an Administrator of your team project has enabled check-in notes, then you can type the information into each field in the Notes section.
Choose the Check In button.
One of the following outcomes occurs.
Administrators of your team project can implement check-in policies to encourage your team to follow best practices. For example, a check-in policy can encourage team members to associate at least one work item with their changes.
In some cases, you may want to override these check-in policies. In the Policy Warnings section, choose Override Warnings.
In the Reason box, explain why you are overriding the policy.
If you are checking in changes into version control folders that are controlled by a gated check-in build, the Gated Check-in dialog box appears.
Choose Build Changes.
For information about how to complete your check-in operation, see Check in to a folder that is controlled by a gated check-in build process.