Cool. I tried to use hg bookmarks once or twice, wanting to use them because of
their light nature that you mentioned and because they seemed like a closer
match to the branches that I'm accustomed to in git.
I stumbled on the Bitbucket part and couldn't figure out how to make it work.
But
I stumbled on the same thing. It's unfortunate that Bitbucket's support for
bookmarks in PRs is lacking. :(
Does any one know if the PR updates automatically when further commits are
made, as Florian, asked?
I have no problem myself in using bookmarks, but the Contributing section
should mention
On 14 August 2014 16:25, Bruno Oliveira nicodde...@gmail.com wrote:
I stumbled on the same thing. It's unfortunate that Bitbucket's support for
bookmarks in PRs is lacking. :(
Yes, that is unfortunate. But note that for a simple contribution, as
explained by the CONTRIBUTING.rst guide, this
On 13 August 2014 17:11, Anatoly Bubenkov bubenk...@gmail.com wrote:
However, it's important to keep the contributing workflow simple and user
friendly. With the need of getting the commit hash on every PR change it
makes the process very annoying IMHO.
True, it would be nicer if bitbucket did
On Thu, Aug 14, 2014 at 6:52 PM, Floris Bruynooghe f...@devork.be wrote:
Yes, that is unfortunate. But note that for a simple contribution, as
explained by the CONTRIBUTING.rst guide, this does not even occur
since you won't be creating more then one head. So one can simply
create the PR
That's true that hg branches are not meant to be used for feature branches,
and that's clearly stated in hg docs, and it's one of the reasons I like
git more.
However, it's important to keep the contributing workflow simple and user
friendly. With the need of getting the commit hash on every PR
Hi!
Same here. Also using the hash, will the PR update if you make further
commits, like it does with a branch?
Regards,
Florian Schulze
On 13 Aug 2014, at 18:11, Anatoly Bubenkov wrote:
That's true that hg branches are not meant to be used for feature
branches,
and that's clearly stated
Hi,
I was wondering if people would be fine with encouraging contributors
to use bookmarks rather then named branches in mercurial for pull
requests. Named branches are rather permanent and more suited for
things like the 2.6.x release branch or permanent things like that.
Bookmarks work really