Share via

Override a Check-In Policy (Team Explorer Everywhere)

  • Article

Some organizations define check-in policies to reduce risks to the application code. These check-in policies require you to take actions when conducting a check in to version control. For example, you might be required to associate a work item with the changeset. For more information about how to check in files, see Check in Pending Changes (Team Explorer Everywhere). The following procedure describes how to override a check-in policy during a check-in process.

Note

The following procedure assumes that you are checking in one or more items that are in violation of a policy that was set for your current team project.

Required Permissions

To perform these procedures, you must have the Check in permission set to Allow. For more information, see the following topic on the Microsoft Web site: Team Foundation Server Permissions.

To override a check-in policy during check-in

  1. Start the process to perform a check-in. For more information, see Check in Pending Changes (Team Explorer Everywhere).

  2. Click the Policy Warnings channel to view the policies in place for your team project. For example, the policy constraint “You must associate your changes with one or more work items” prevents users from submitting changes that are not associated with a specific bug or task for which they are submitting a change.

  3. Check in the items that are in violation of the policy for your team project. The Policy Failure dialog box appears.

  4. Select the Override policy failure and continue check-in check box.

  5. In Reason, type an explanation that describes why you need to perform the check-in in violation of the set policy.

  6. Click OK.

    The specified changes are checked in to Team Foundation version control.

See Also

Other Resources

Submitting and Undoing Pending Changes (Team Explorer Everywhere)

Setting and Enforcing Quality Gates (Team Explorer Everywhere)