Effects of Status on Check-ins and Check-outs

During the file check-out process, the application copies a file revision from the repository to a working folder. Checking in a file places a new revision in the repository. In many cases, the status of a file affects the check-in or check-out process.

Status Check-in Check-out
Current No considerations. No considerations.
Deleted on Disk

Not applicable.

If a file has a Deleted on Disk status, it is not in your working folder, so it cannot be checked in.

No considerations.

If a file has a Deleted on Disk status, you are asked if you want to check it out when you open it. You can also check it out manually.

Deleted on Server

Not applicable.

A file with the Deleted on Server status cannot be checked in. You can add it to the project with the Add Files command.

Not applicable.

A file with the Deleted on Server status is not in the project view, so it cannot be checked out.

Ignore

Not applicable

Files with the Ignore status can be checked in. However, marking them as Ignore indicates that you do not want to work with the file.

Not applicable

Files with the Ignore status can be checked out. However, marking them as Ignore indicates that you do not want to work with the file.

Merge

Starts File Compare/Merge unless you force the check-in.

The Merge status means that someone else has checked in this file since your last check-out. You do not have their changes in your working file and someone’s changes will

Your changes will be lost if you check out this file.

You may be able to merge the tip revision and your working file using the application in which this file was created, for example, Word for Windows. If the file is a text file, try a check-in operation.

Missing

Not applicable.

If a file has the Missing status, it is not in your working folder so there is nothing to check in.

No considerations.

If a file has the Missing status, you are asked if you want to check it out when you open it. You can check it out manually, too.

Modified

No considerations.

Unless someone else has the file locked, you can check in the file.

No considerations.

Unless someone else has the file locked, you can check out the file.

Modified on Disk and Deleted on Server

Not applicable.

A file with the Modified on Disk and Deleted on Server status cannot be checked in. You can add it to the project with the Add Files command.

Not applicable.

A file with the Modified on Disk and Deleted on Server status is not in the project view, so it cannot be checked out.

Not in View

Not applicable.

A file with the Not in View status cannot be checked in. You can add it to the project with the Add Files command.

Not applicable.

A file with the Not in View status is not in the repository, so there is nothing to check out.

Out of Date

Not allowed unless you force the check-in.

Checking in an Out Of Date file means that the tip revision no longer has the changes made to the file since the time your working copy became Out Of Date.

No considerations.

Checking out an Out Of Date file makes your working file Current.

Unknown

Not allowed unless you force the check-in.

If the file’s status is Unknown, the consequences of this action are also unknown. Your working file becomes the tip revision in the repository. Use Update Status with an MD5 checksum to see if the file can be identified.

You might want to compare your working file to the tip revision if this is not successful.

Allowed if you merge the file with the tip revision. However, because the very first revision is used as the ancestor file for this merge, it is likely that many, many things appear to have changed or be in conflict. You may prefer to force a check-out (or force a check-in).

If the file’s status is Unknown, the consequences of this action are also unknown. Your working file is overwritten by the tip revision in the repository. Use Update Status with an MD5 checksum to see if the file can be identified.

You might want to compare your working file to the tip revision if this is not successful.