MERCURIAL WINDOWS HOOK EXAMPLE INSTALL
MERCURIAL WINDOWS HOOK EXAMPLE UPDATE

Init your project, add files, see changes and commit them. To start a new project, you initialize a repository, add your files and commit whenever you finished a part of your work.ДЄlso you check your history from time to time, so see how you progressed. It works just like the log keeping workflow, with the difference that you go back to earlier changes at times and work onwards from there. The second workflow is still very easy: You're a lone developer and you want to use Mercurial to keep track of your own changes and optimize your workflow. Lone developer with nonlinear history Use case To also see the diff of the displayed revisions, there's the -p switch (-patch) $ hg log -p -r 3 To see a certain revision, you can use the -r switch (-revision). Summary: Say Hello World, not just Hello. Now you add a new folder in which you want to work: $ hg init projectД®nter the project folder, create some files, then add and commit them. For that you open the file ~/.hgrc (or mercurial.ini in your home directory for Windows) with a text-editor and add the ui section (user interaction) with your username: Workflow Prepare MercurialДЄs first step, you should teach Mercurial your name. It shows the basic techniques for more complex workflows.

This workflow only requires an installed Mercurial and write access to some file storage (you almost definitely have that :) ). The first workflow is also the easiest one: You want to use Mercurial to be able to look back when you did which changes. Those further down build on previous workflows. We go from simple to more complex workflows. Basic command line abilities are helpful, because we'll use the command line client. It's really more of a UI thing, but it might come back and bite you long after you've started this system.This guide doesn't require any prior knowledge of version control systems (though subversion users will likely feel at home quite quickly). That works fine when you have 10 or 20 of them, but fails when you have 5,000 of them. Mercurial itself scales fairly well with the number of named branches, but many tools expect to be able to show all branches in a single drop-down menu. Using commit messages is better than using named branches if you plan to have thousands of bug numbers. Make it a custom script that will ask for a bug number, put that into a commit message template and then start and editor to let the developers enter the commit message. Validating the commit message is best done by configuring ui.editor. There wont be any online validation, but they can follow pretty much the same workflow as in Subversion. You can also ask the developers to put the bug number into the commit message, just like with Subversion.

MERCURIAL WINDOWS HOOK EXAMPLE UPDATE

When pushing to the server, it's easy to parse the pushed changesets (in a changegroup hook) and update Bugzilla. The following commits will then contain the 'bug-123' label inside them. Have your developers run $ hg branch bug-123Д«efore starting work on bug number 123. This can be done with named branches in Mercurial. There wont be anything in the changesets that tie them to a Bugzilla bug - it's only Bugzilla that knows that changesets belong to what bugs.ДЄnother way would be to embed the bug numbers into the changesets themselves. That is one way of associating changesets with an external issue tracker. When the developer enters the bug number, the script can look at hg outgoing and associate the outgoing changesets with the bug in Bugzilla. The pick-bug-number.sh script should first check that the developers are pushing to your central repository (and not, say, to some other repository on their laptop) and then ask them for a bug number.

MERCURIAL WINDOWS HOOK EXAMPLE INSTALL

So you could ask the developers to install a hook like However, hg push is of course a good time to go and update Bugzilla since the developers are online when pushing to the central repository. The push command is only moving changesets around, not changing them. The important thing to remember is that changesets are (nearly) immutable, which means that it's too late to add a bug number when the developers are running hg push.

Mercurial windows hook example