This extension is not distributed with Mercurial.
Author: Scott Chacon, Augie Fackler, Abderrahim Kitouni, and Sverre Rabbelier
Mailing list: https://groups.google.com/group/hg-git
Old web page: https://hg-git.github.io/
This extension adds the ability to work on a Git repository from Mercurial. It also allows using a Git server as a collaboration point for a team with developers using both Git and Mercurial. At the same time, it can also be used to interact with a hg repository using git.
It can convert commits/changesets losslessly from one system to another, so you can push from a Mercurial repository and another Mercurial client can pull it and their changeset node ids will be identical - Mercurial data does not get lost in translation. It is intended that Mercurial users may wish to use this to collaborate even if no Git users are involved in the project, and it may even provide some advantages if you're using Bookmarks (see below).
This plugin is entirely in Python - you do not need to have Git installed on your system. The only dependency is Dulwich Python library.
To install hg-git, for example in ~/.hgext directory.
hg clone https://foss.heptapod.net/mercurial/hg-git ~/.hgext/hg-git
hg --config extensions.hggit=~/.hgext/hg-git/hggit version -v
There should be no errors, and hg-git version should be visible.
Configure your .hgrc to enable the extension by adding following lines:
[extensions] hgext.bookmarks = hggit = /path/to/hg-git/hggit
You can clone a Git repository as you would clone a mercurial repository, for example :
hg clone git://github.com/schacon/hg-git.git
will clone the git mirror of the hg-git repository in a directory named 'hg-git.git'.
TODO: document the difference between ssh://host/path and host:path git urls and how they map to hg.
If you want to clone a repository via ssh, you can do so using a git+ssh:// protocol prefix :
hg clone git+ssh://email@example.com/schacon/hg-git.git
This will also create a bookmark for each git branch, and add local tags default/<branch name> for each branch. This is similar to origin/<branch name> in git.
When you pull from a git repository in the [paths] section of hgrc, it will "fast-forward" the bookmarks if the branches haven't diverged. It will also create local tags as above.
When pushing to git, the following is done to determine what's pushed :
- if there are no bookmarks and the remote repository is empty, the tip is pushed as the master branch.
- for each branch in the remote repository, if there is a bookmark or a tag with the same name that points to a descendent of the head, then push it.
- if there are bookmarks with no remote branch, a new branch is created.
Using hg-git to interact with a hg repository with git
TODO: this section is outdated (references to master branch and exportbranch config)
You can create a local .git repository like this:
Editr the .hg/hgrc (or your ~/.hgrc if you want to make this the default):
Then do the following from in the hg repository:
This will create a .git repository in the working directory (alongside the .hg directory) that you can interact with like any regular git repository. If you have made commits in the git repository and want to convert them to hg commits, first make sure the changes you want are on the master branch, then do:
This will put your changes on top of the current hg tip.
Optionally you can change your hgrc to include an exportbranch statement:
[git] intree=1 exportbranch=refs/heads/from-hg
This will cause 'hg gexport' to update the 'from-hg' branch, instead of the master branch, so that your changes will not be lost even if you work on the master branch.
TODO: this section is outdated
If you want to help with the development of hg-git, here are some things you can help with :
- push/pull -r
better handling for tags (see this thread on the mailing list).
- make pushing using dulwich more efficient (faster packing, thin packs, etc).