WordPress Hg

I’ve really caught the Mercurial bug recently and have begun chewing coworkers’ ears off about its benefits. I’ve been looking into ways to integrate it into my WordPress-related efforts and, inspired by this recent post on the WP Devel blog announcing a github effort to make WP available via git, I decided to set up an Hg clone (haw!) of the core WordPress codebase.
It’s available here over on BitBucket and, unlike Nikolai’s effort (which only appears to track trunk), I started my clone at the root of the Subversion repository, meaning that all branches and tags are (theoretically) accounted for. I’m currently syncing the two repos by-hand but am working on an automated process that should push changes from the core WordPress SVN server to BitBucket fairly quickly.
I’ll post again later to demonstrate my full process for accomplishing this — it was astonishingly easy, to be honest.
In the meantime, get cloning!

Default image
Doug
Husband & father with youngins; Presbyterian; Will devops for boardgames; Dadjoke Enthusiast; Longtime WordPress user; The failure mode of “clever” is...

2 Comments

  1. Do you also use Mercurial to keep track of your projects? With the term “project” defined as “a plain WordPress installation, various own and third party plugins, and a theme by an external designer.” While leaving content (blog postings, images, etc.) out of the project, (yet in the backup).
    Am thinking of building a revision/version of a project/website from various project related repositories from internal and external contributors for testing, and deploying. And maybe put the configuration of the build in a Mercurial repository to be able to track the versions of included projects.
    Looking forward to learn from your experience as hg bugger 🙂

  2. @onezero:
    No, not yet, but it’s definitely something I’m looking to start doing in the very near future…

Comments are closed.