In this page, specify whether you want CLion to ask you for confirmation before performing specific version control related actions.
|When files are created||In this section, specify whether and how to put a file created in CLion under version control. The following options are available: |
|When files are deleted||In this section, specify whether and how to remove a file from the version control system when the file is removed in CLion. The following options are available: |
|When empty changelist becomes inactive||In this section, specify CLion behavior on deleting an empty changelist. |
|Display Option dialogs when these commands are invoked|| In this area, specify whether you want CLion to ask you for confirmation when invoking commands, specified below. To enable showing a prompt before performing an action, select the relevant check boxes. |
|Show Clear Read-Only Status dialog box||Select this check box to have CLion explicitly require cancellation of the read-only status when you open a file in the editor and try to modify it. |
The read-only status can be cleared in two ways:
This option is relevant for those version control systems that separate check-out from opening for editing.
|Suggest to move uncommitted changes to another changelist||When this option is selected, on committing a changelist to the repository with some files excluded from the commit, CLion prompts to move these files to another changelist.|
|Force non-empty check-in comments||Select this check box to suppress committing changes without supplying them with corresponding comments.|
|Clear initial commit message||If this check box is selected, the previous check-in comment is cleared from the Comment area.|
|Show patch in explorer after creation||Use this drop-down list to define the CLion behavior when a patch is created. The available options are: |
|Create changelist on failed commit||Use this drop-down list to define the CLion behavior in case of failed commits. The available options are: |
See the section Resolving Conflicts.