You are here: Modifying Files > Checking in updated files

Checking in updated files

Check in updates files with changes, removes the lock on the files, makes changes available to other users, and increments the version number by one.

Check in files whenever you are able to successfully build with the changes and your changes do not break other areas of the code. If you use multi-user check outs, it may be necessary to merge files frequently. Checking in regularly reduces the complexity of these merges, making it easier to resolve conflicts. Checking in often also allows other users to access changes.

1. Select the files or repository and choose Activities > Check In.

The Check In Files dialog box opens.

2. Enter any Comments, such as changes made to the files.

3. Select Apply comments to all to use the same comments for all files.

If you clear this option, the Check In Comments dialog box opens after the first file is checked in. You can enter a separate comment for each remaining file to check in or select Apply comments to remaining files to apply a comment to all remaining files.

4. Select Recursive to check in files from the selected repository and all subrepositories.

5. Expand and select any additional check in options.

6. Click Differences to view differences between the file you are checking in and the working directory copy. See Viewing file differences.

7. Click Attach to attach files to an item in TestTrack or an external issue tracking tool. See Attaching source files to TestTrack items or Attaching source files to external issues.

8. Click OK.

Surround SCM automatically merges changes when files are checked in. If there are conflicts, the merge application opens. See Merging files.

 

Additional documentation  Knowledgebase  |  Blog  |  Technical support