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.
If multiple users can check out files, you may want to check in and 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.
Changelist options
Select changelist options to check in files as part of a changelist. See Adding file actions to changelists.
Code review options
Select Add new version to code review to add the updated file versions to a code review. Select a code review from the list or select <New code review> to create a new code review. See Creating code reviews. Click Select to view code review details and determine which review to add the files to. See Selecting code reviews.
Note: If you are checking in files as part of a changelist, the files are added to the code review after the changelist is committed.
Local file options
Select local file options to indicate how to handle local files after the check in.
Advanced options
Select advanced options to change workflow states, label files, skip the merge process, and update version numbers when files are checked in.
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 Helix ALM or an external issue tracking tool. See Attaching source files to Helix ALM items or Attaching source files to external issues.
8. Click OK to check in the files.
Surround SCM automatically merges changes when files are checked in. If there are conflicts, the merge application opens. See Merging files.
Note: If you changed the workflow state for the files, you may be prompted to enter an electronic signature and reason. See Entering electronic signatures. You cannot set a state that requires an electronic signature on files if a merge is required. If you need to change the state, clear Change state when version updated, check in and merge the files to resolve conflicts, and then manually change the state. See Changing workflow states.
    |
|