Checkout the Last Public Revision with Mercurial

By  on  

I've always preferred git over Mercurial (hg) because the feature branch workflow makes organizing code and working off of master very easy. You don't get that with vanilla mercurial -- instead, commits can just sort of apply on top of each other, without much organization. Sometimes mercurial can feel a bit chaotic.

When working on Mozilla's mozilla-central repository (for your beloved Firefox!), I always start new commits off of the latest public commit. "public means it has been merged into mozilla-central, "draft" means it was created locally and is only on my machine.

Getting the last public revision ID required a bit of command line hackery and search so I found a better way to check out the last public revision:

hg checkout -r 'last(public())'

That command is a bit much to remember so I created an alias in my .bash_profile:

alias hgmaster='hg checkout -r “last(public())”’

As with every alias I create, whether a git alias or a bash alias, I wish I had created this sooner -- I'd have saved so much time!

Recent Features

  • By
    5 More HTML5 APIs You Didn’t Know Existed

    The HTML5 revolution has provided us some awesome JavaScript and HTML APIs.  Some are APIs we knew we've needed for years, others are cutting edge mobile and desktop helpers.  Regardless of API strength or purpose, anything to help us better do our job is a...

  • By
    Page Visibility API

    One event that's always been lacking within the document is a signal for when the user is looking at a given tab, or another tab. When does the user switch off our site to look at something else? When do they come back?

Incredible Demos

  • By
    Create a NoScript Compatible Select Form Element with an onChange Event

    I wouldn't say that I'm addicted to checking Google Analytics but I do check my statistics often. I guess hoping for a huge burst of traffic from some unknown source. Anyway, I have multiple sites set up within my account. The way to...

  • By
    Submit Button Enabling

    "Enabling" you ask? Yes. We all know how to disable the submit upon form submission and the reasons for doing so, but what about re-enabling the submit button after an allotted amount of time. After all, what if the user presses the "stop"...

Discussion

  1. Jeremy

    What do you mean you can’t use the feature branch workflow with Mercurial?

    • I guess branches are different with Mercurial, and that bookmarks don’t feel the same as branching off of master. Could just be me.

  2. glob

    It would be simpler/quicker to instead do:

    hg checkout -r 'last(public())'
  3. agentgt

    You can also use mercurials excellent revsetalias and alias support:

    [alias]
    master = update -r 'last(public())'
    
    [revsetalias]
    master = last(public())
    wip = (parents(not public()) or not public() or . or head()) and not closed()
    

    Now You can do

    hg update master
    

    or

    hg master
    

    I added the revset alias wip as well which shows the changes you haven’t yet pushed to master.

    Finally for lightweight branches I highly recommend the evolve extension and just making normal mercurial named branches that you only push to your local mutable (non publishing repository). So long as the branches are in draft you can delete them which will be the case if the repository is non publishing.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!