It is good practice to get a file lock before editing a file. The lock tells other users that the file is being edited, and you can avoid merge issues. When you set up source control, you can configure SVN to make files with certain extensions read only. Users must get a lock on these read-only files before editing.
In the Current Folder browser, select the files you want to check out. Right-click the selected files and select Source Control > Get File Lock. A lock symbol appears in the source control status column. Other users cannot see the lock symbol in their sandboxes, but they cannot get a file lock or check in a change when you have the lock. To view or break locks, right-click in the Current Folder browser and select Source Control > Locks.
If you see an SVN message reporting a
locked error, remove stale locks. In the Current Folder browser,
right-click and select Source Control > SVN Cleanup. SVN uses working copy locks internally and they are not the file locks
you control using Source Control > Get File Lock.
Starting in R2020a Update 5, SVN cleanup only removes stale locks and unfinished transactions. It does not remove unversioned or ignored files.
You can manually remove unversioned and ignored files.
In the Current Folder browser, click the SVN header to sort files by their SVN status.
Select the Not Under Source Control files.
Right-click and select Delete.
To manage global SVN locks for a repository, from the top-level repository folder, right-click the white space (any blank area) in the Current Folder browser and select Source Control > Locks.
In the SVN Repository Locks dialog box, you can:
View which users have locks on files.
Right-click to break locks.
Group locks by user or file.