Check in changes to the server
Check in changes you make to the server to make the changes available for other users in your repository.
When you edit your files with an external tool and save them, Gluon detects these changes. When you refresh your workspace view, the status of any edited files changes from Checked-out (unchanged) to Checked-out (changed).
The Checked-out (changed) status means that the changes to the locked files are saved locally but not on the server. To unlock the file and allow other users to access the changes, you need to check in the changes:
- Select the Checkin changes tab.
- Select any files that you want to check in.
- Write a comment to identify the changes associated with the files.
- Select Checkin.
The Checkin changes tab also displays the differences of any file that you select to show you the changes made.
After you check in your changes, the status of the file in the Explore workspace tab returns to Controlled. The changeset is also available in the details view.
Note: To check in changes via the command line, run the command cm partial checkin.
Keep files locked
You can check in your files so that the changes are available on the server, but keep the file locked so that you can continue work on the file later.
Before you select Checkin, select the Keep items locked checkbox.
Note: To keep an item locked from the command line, run the command cm partial checkin and add the--keeplock option.