File is removed from the working tree thus not revisioned anymore.
The file is still present in the repository.
The file could be deleted from the filesystem depending on the provider.
Will checkouts using this repository be persisted so they can
be refreshed in the future? This property is of concern to SCMs
like Perforce and Clearcase where the server must track where a
user checks out to.
File is part of an update transaction with the repository.
Note: ADDED and REMOVED are not an update status since they indicates
that the working tree has changed.
An update indicates the opposite, that the repository was changed compared to
the working tree and that it is now synchronized unless there are conflicts.
Typesafe enum for file status
There are two types of status defined in this class:
1) Status: Changes in the working tree, not yet committed to the repository eg.