Checking in a file creates a new revision in the archive if the file has been modified, and releases the lock on the file. By default it will also make the local copy of the file read-only so that it can't be modified.
 Because other developers may use the files you check in, it is important to make sure that they at least compile before checking them in.
|
To check in a file from within your development tool (depending on the interface), make that file the current one and select Workgroups / Checkin from the main menu. To check in file(s), folder(s), or a project from within Version Manager, select the relevant objects and right-click, or select Action, and select Checkin.
You will be presented with the check in dialog box to allow you to assign a Version Label to the files and to specify what to do once the files are checked in:
|
Comments - Enter comments to describe the changes made to the files being checked in. These comments will be applied to all files being checked in. Right-clicking in this box allows you to retrieve previously entered comments.
Version Label – If you want to attach a Version Label to the new revision of the file once it is checked in, select a Version Label using the ellipsis (...) button. The Version selection dialog box allows you to create a new version label.
| The Version Label list will only display visible labels. To use a label that is marked as hidden, use the button with the ellipsis (...) to select it
|
Move existing version label to new revision – If you wish to move an existing Version Label to the new revision, check this box. If the Version Label you are assigning to the file already exists for a file, it will be removed from it's existing revision and attached to the revision created when the file is checked in.
Force Branch on the new revision – If the file being checked in is not to become part of the main development stream, check this box. When the file is checked in, a branch revision will be created.
| If the Label you are attaching to the new revision has an associated Branch Base Label (see Version Labels), both the 'Move Existing' and 'Force Branch' options will be disabled. This is because branching will be handled automatically.
|
Prompt for Comments for each file - Checking this option, you can assign comments for each modified file being checked in. If this is left unchecked, the comment entered will be applied to all files being checked in.
|
Checkin if Unchanged - If this option is checked (default), all locked revisions will be unlocked whether or not there are any changes to the file. If this is unchecked, all unchanged files will remain locked.
Maintain a Lock on the new revision - If this option is checked, once the file is checked in, the new revision of the file will be locked again. This allows you to check in changes to allow others to get these changes while keeping a lock on the files to continue working on them.
Once Checked in
Leave the local file readonly - Once the file is checked in, the local copy of the file will be made readonly to prevent accidental modification.
Delete the workfile – once checked in, the local workfile will be deleted.
Make the file writable – once checked in, the local workfile will be left writable, but the archive will not be locked.
Default – Check this box to make the current settings in the Options page the default settings for subsequent check in actions.
|
Difference - Switching to the Files page of this dialog allows you to check what changes were made to any of the files being checked in. Selecting a file and pressing the Difference button will execute the Difference Viewer against this file.
Pressing the OK button will check in the relevant files. The state of any local workfiles will be dependent on the options you select above.
See also: Scenario 3
© 1995-2018 MCN Software