This site serves as node for gathering useful workflows.

If you use a workflow which isn't yet listed here, please add it.

And if you use a workflow very similar to one of the workflows here, but with distinct changes, please add a note to the modifications section of the existing workflow.

Intro

With Mercurial you can use a multitude of different workflows. This page shows some of them, including their use cases.

It is intended to make it easier for you to create your own workflow.

We begin with standard workflows and then go on to more complex examples.

The initial workflows come from the [http://bitbucket.org/segv/hg-website/wiki/Workflows workflow collection] in the wiki for [http://mercurial-scm.org] - would you like to help us convert one of the remaining ones to this page? (please delete this line, as soon as all workflows are transferred).

The workflows on this page are rather terse to give you a good overview. You can find a longer introduction which shows basic Mercurial usage compatible with these workflows in [http://mercurial-scm.org/learning_mercurial_in_workflows learning Mercurial in workflows].

Structure or a workflow

Sorting of the entries

Overview and plan

General:

collaborating on features:

Dependency tracking:

Special usages

working with other vcs:

neat tricks for smoothing workflows:

Workflows

One-off patch submission

For whom?

If you just want to submit a short patch to a project, this workflow is right for you.

Requirements

You need just Mercurial (command line) and an email address to which you can send the patch.

Local Flow

First get the repository

$ hg clone http://hg-scm.org/hello

Now edit the files and commit your changes

$ cd hello

$ (edit files)

$ hg add (new files)

$ hg commit -m 'short description of the changes'

Export your patch

$ hg export tip > patch.diff

Note: "tip" is the most current revision in your repository. hg export exports all selected revisions as one change.

Sharing changes

To share your changes, just send the file patch.diff to the developers email address, ideally with a description what your patch does and why it's important.

The developer will then import and test it:

$ cd hello

$ hg import patch.diff

Now he has the revision in his local repository.

Note: You can also use hg import on a maildir file. It will automatically select and import the patch.

Modifications

You can also upload the patch, for example to a bugtracker. It's just a simple file after all.

Lone Developer

...