![]() The mixed-revision state of a working copy may affect the Move and Rename refactoring applied to folders, in which case items in revisions different from the moved subtree root will be tracked separately, which can be confusing. Enabling this option will help prevent your working copy against the mixed-revision state. Select this checkbox to automatically update your project after the commit. The checkbox is only available if the FTP/SFTP/WebDAV Connectivity plugin is enabled. Select this checkbox to always upload files to the selected server or a server group. The list is only available if the FTP/SFTP/WebDAV Connectivity plugin is enabled.Īlways use selected server or group of servers To add a server configuration to the list, click and fill in the required fields in the Add Server dialog that opens. You can select a tool from the list, or click the Browse button and configure an external tool in the External Tools dialog that opens.įrom this list, select the server access configuration or a server group to use for uploading the committed files to a local or remote host, a mounted disk, or a directory. These controls are available for the following version control systems:įrom this list, select the external tool that you want IntelliJ IDEA to launch after the selected changes have been committed. Use the controls in this area to define which additional actions you want IntelliJ IDEA to perform before committing the selected files. ![]() The list in the bottom of the area displays the jobs that are currently attached to the selected changelist. Otherwise, to select a job among several available jobs, click the button and find the desired job using the Edit Jobs Linked to Changelist dialog. If only one job matching the pattern is found, it is attached to the changelist automatically. In the field, specify the exact name of the job or a search pattern according to the Perforce jobs syntax rules. ![]() Unlink selected jobs: click this button to detach the selected job from the changelist.Įdit associated jobs: click this button to open the Edit Jobs Linked to Changelist dialog where you can search for available jobs, view their details, and link jobs to the selected changelist.įind and link job matching the pattern: click this button to start quick search for the job that matches the pattern specified in the field and attach the job to the changelist. Use the controls in this area to search for Perforce jobs, link jobs to the selected changelist, and detach the currently linked jobs. These controls are available only if you select the Enable Perforce Jobs Support checkbox on the Perforce settings page. The controls in this section are located in the top-right part of the dialog, and contain the options that are specific for the version control system you are using. You can click Commit Message history Ctrl M to choose from the list of recent commit messages. This comment will also be used as the name of the patch file, if you decide to create a patch. You cannot commit your changes until you enter some description in the Commit Message field. In this area, enter a comment to the current commit. This area also shows how many files of each type are shown, and how many of them will be committed. The summary under the modified files pane shows statistics on the currently selected changelist, such as the number of modified, new, deleted and unversioned files. The active changelist is selected by default. ![]() These buttons are not available in flat view.įrom this list, select the changelist that contains the modified files to be checked in or included in the patch. Revert all changes made to the local working copy of the selected files.Ĭlick this button to reload the Changed files tree view so it is up-to-date.Ĭhoose how you want to group the modified files - by directory or moduleĬlick these buttons to expand or collapse all nodes in the directory tree. Alternatively search for the config key in the settings UI to change its value.Open the Differences dialog that highlights the differences between your local working copy of the selected file and its repository version. To change any of these, add the relevant Config key and value to your VSCode settings.json file. Here are all of the extension settings with their default values. Please use a dedicated extension like blamer-vs Settings You will be asked for the URL of the repository and the parent directory under which to put the local repository. You can checkout a SVN repository with the SVN: Checkout command in the Command Palette ( Ctrl Shift P).
0 Comments
Leave a Reply. |