This project is read-only.

Add "Select head change set" option to "Create fork" page


I really like the new Mercurial fork feature: .

But it has one downturn: There is no way to specify which change set is base for the patch. If you develop patches for software, it's common to develop the patch against a specific build version and not the latest check-in.

To handle this it would be great to have the ability to select a release when creating a fork which shows all releases having an associated change set. Perhaps something like this.

Select head change set:
o Latest
o Release [MySoftware v1.0 [v]] {drop down}

o Specify Change set [ 73ds6a6s7] {text box}

Greetz Felix


matthaw wrote Mar 5, 2010 at 7:02 PM

Hi Felix,

I realize other sites have this functionality, and was wondering does this make forking easier vs running an update to that revision command after cloning?


fkollmann wrote Mar 5, 2010 at 8:24 PM

Hi Matt,

good point from your side. I personally would prefer to have this more straight forward and creating a best-practice-UX because you cannot expect the developer to be familiar with Mercurial or experienced with open source development (like choosing the release revision). So my POV is that adding the functionality to the create-fork-site adds less complexity than doing the update-to-revision solution.

But of course you're right that this should not be an issue for experienced developers or if correctly mentioned in how-to-contribute-tutorials/faqs.

Greetz Felix

attilah wrote Mar 9, 2011 at 5:08 PM

From my side I'd like to have a list of changesets and a branch selector for pull request creation. And having multiple pull requests should be also a good thing.

If a project is REQUIRING 1 fix / pull request then it slows all things down.

If you're fixing in multiple branches you can not push your changes to the server before you created a pull request for your other branch fixes...

So there are a lot of doable things in this area to make it really useful!

Now I'm about to close and recreate my fork since it's messed up because of the disablility to exclude branches from pushed changes :-(