This section is for users familiar with the scripting interface of their version control system. If you are unsure of how this works, please don't try to edit the scripts as this could cause serious problems.
Note that you cannot create repositories or download local working copies of your project from your repository from within Help+Manual. Those are tasks that must be performed with your version control software. See the sections on Git and SVN for details.
If you are familiar with scripting and the API of your VCS, reading the scripts should be pretty self-explanatory.
The scripts referenced in the Version Control settings in the Program Options are stored in the \Tools\ sub-folder in the Help+Manual program folder. They are editable, but we strongly recommend making a copy and using the Custom Command File option to refer to your version instead of changing the original.
On opening, control jumps to the section specified by the command, executes all the operations there on the project folder with the VCS executable, and then exits.
You should have sections for all the possible commands in your script (get|sync|checkout|checkin|status), since those commands can always be issued by Help+Manual.
The Git script uses "main" as the default branch
Note that the Git script uses "main" as the default branch for your repository. If this is different in your case, you need to change the branch reference in the script.
This script is an empty template. You need to add all your own operations under the respective command labels. The way it is called also differs from the scripts for Git and SVN in that Help+Manual itself does not call the VCS executable. This means that you need to include that in your own commands under the individual labels.
For example, if you are using tf.exe for Team Foundation Server, and you have added its path to your Windows environment variables, your sync section could look liked this (the %3 variable inserts your project folder path):
