Set up a local Mercurial repository

Although Mercurial provides high flexibility in arranging data and your work with repositories, the following scenarios are most commonly used for setting up a local Mercurial repository:

Clone an existing remote repository and create a new project with the downloaded data.
Create a local repository which you can push to a remote location later, if necessary.

Clone a remote Mercurial repository

From the main menu, choose VCS | Get from Version Control. The Clone Mercurial Repository dialog opens.
In the Get from Version Control dialog, select Mercurial from the Version control list and specify the URL of the remote repository you want to clone.
Click Clone. If you want to create a DataSpell project based on the sources you have cloned, click Yes in the confirmation dialog.

To create a local Mercurial repository

Open the project you want to store in a repository.
From the main menu, choose VCS | Import into Version Control | Create Mercurial Repository. The Create Mercurial Repository dialog opens.
Specify the location of the new repository.
- To have the repository created in the project root, choose the Create repository for the whole project option. DataSpell will create the .hg directory in the project root folder.
  This option is selected by default.
- To have a new repository created in another location, choose the Select where to create repository option and specify the path to the repository location in the field below. Type the path manually or click Browse and choose the relevant folder in the Select directory for hg init dialog that opens.
  Mercurial does not support external paths. So if you choose another directory, note that it must contain the tree where the project root resides.
  If you choose a directory which is already under Mercurial control, DataSpell opens the Directory Is Under hg dialog, where you can choose to create a repository in the specified location or to stay in the parent repository.
Put the required files under Mercurial version control. The files appear in the Local Changes view under the Default node.
Note that if you specify Mercurial as the version control system for a directory in the Version control settings dialog, DataSpell will suggest to put each new file in this directory under Mercurial control.

Last modified: 19 March 2022