#MERCURIAL WINDOWS TUTORIAL FULL#

Now is the point where you prepare a snapshot of the changes before committing them to the official history. Save the file as supplies.txt to the bitbucketstationsupplies directory on your local system. The supplies.txt file now appears in Sourcetree since you created it in your local repository. Use a text editor to add the following three lines: If you aren't sure which one to go with, keep Git as your option.Ĭlick Create repository. Bitbucket creates your repository and displays its Source page.ĭouble-click the bitbucketstationsupplies repository in Sourcetree and notice that there is nothing to commit from your local repository to the remote repository. Include a README? -If you recently created your account, this defaults to a tutorial README. For the purposes of this tutorial, pick either of the Yes options, that way you'll start out with a file.įrom Version control system, you can choose either Git or Mercurial. If this box is unchecked, anyone can see your repository. Keep the rest of the options as is unless you want to change them:Īccess level -Leave the This is a private repository box checked. A private repository is only visible to you and those with access. For example, if the user the_best has a repository called awesome_repo, the URL for that repository would be. Bitbucket uses this Name in the URL of the repository. With the exception of the Repository type, everything you enter on this page you can later change.Įnter BitbucketStationSupplies for the Name field.

Take some time to review the dialog's contents. Bitbucket displays the Create a new repository page.

From Bitbucket, click the + icon in the global sidebar and select Repository.

Information messages concerning the results of executing generated Mercurial commands.Do the following to create your repository: When using Mercurial integration, it is helpful to open the Console tab of the Mercurial tool window Alt+9, which displays the following data:Īll commands generated based on the settings you specify through the P圜harm user interface.

Modifications results are shown in the Commit tool window Alt+0. See File status highlights for file status highlighting conventions. The files in the folders under the Mercurial control are highlighted according to their status. When Mercurial integration with P圜harm is enabled, the Mercurial item appears in the VCS menu, and in the context menus of the editor and Project tool window. You can access the remote repository through a pair of ssh keys or apply the username/password and keyboard interactive authentication methods supported by the Mercurial integration. If you want to use a remote repository, create a Mercurial hosting account first. Mercurial integration is enabled for the current project root or directory.

#MERCURIAL WINDOWS TUTORIAL FULL#

In this case, you can specify only the executable name, the full path to the executable location is not required. It is recommended that you add the path to the Mercurial executable file to the PATH variable.

If you followed the standard installation procedure, the default location is /opt/local/bin or /usr/local/bin for Linux and macOS and /Program Files/TortoiseHG for Windows. The location of the Mercurial executable file hg.exe is correctly specified on the Mercurial page of the Settings/Preferences dialog.

Mercurial windows tutorial