Checkouts
Unity DevOps Version Control (UVCS) automatically detects any changes to a file within your current workspace and adds them to your pending changes. To notify that you want to make changes to specific files, check out these files. You might want to check out a file for various reasons:
- If you work with locks, you might need to check out files before you edit them. For more information, refer to [Configure exclusive checkout (locks)](https://docs.plasticscm.com/administration/plastic-scm-version-control-administrator-guide#Chapter7:Configuringexclusivecheck-out(Lock).
- If you work with a large codebase of, for example, more than 500,000 files, checkouts can speed up your operations. Instead of searching through your entire workspace for changes, UVCS can list the files in the checkout list without accessing the disk.
To then merge your changes, you can check them in as normal. For more information, refer to Check in changes.
Types of checkout
To check out a file in the Workspace Explorer tab, right-click the file and select one of the following types of checkout:
| Option | Description |
|---|---|
| Checkout | If the file path matches the configured lock rules, the checkout operation locks the file. If the file path doesn’t have the lock rules, then the checkout is a local operation that doesn’t lock the file. |
| Lock and checkout | Lock and checkout adds the file path to your configured lock rules so that the file locks regardless of the original lock rules. |