Renaming a commit with Mercurial before pushing

A quick and short tip for Mercurial, just an excuse for testing Scribefire with the new Java.Net platform. You have previously seen my posts praising the possibility of working in asynchronous fashion with Mercurial. In short, you can commit while disconnected, and push a batch of commits when you're connected again. Now, there's a (small?) issue. When you commit some changes, it's a good practice to put into the commit message a reference to the issue you're working at - I mean precisely the Jira (or such) issue code, such as JRW-123. This is useful because there are many ways to integrate a source code repository with Jira, so the issue in Jira gets some comments (or even explicit links) to the commit into the repository. Problem: if you're disconnected and performed a major refactoring that you want to document in Jira, how do you get the issue number? You can't, and it seems you have to postpone the commit, waiting to have the connection back, so you can enter the issue in Jira and get the issue code. Such a case happened to me today as in the afternoon I did a major refactoring in jrawio, changing the name of two packages, but I forgot the internet connection dongle at home. Mercurial async mode jeopardized? Not at all. This afternoon I committed as usual, without putting any Jira reference in the comment: fritz% hg commit -m "Renamed it.tidalwave.imageio.raw : ...imageio.craw, it.tidalwave...

Date: September, 03 2009
Url: http://www.java.net/blog/fabriziogiudici/archive/2009/09/03/renaming-commit-mercurial-pushing-0

Others News