0
votes

I'm not sure if this is a problem with Mercurial or TortoiseHG (both version 3.6.1) but I've got an issue where revisions pulled from our RhodeCode server have recently started being given "draft" phase on one particular development machine.

My own machine is pulling revisions and marking them correctly as "public", but my colleague always get "draft". We are unaware of any recent changes to his configuration, and we've compared mercurial.ini and the hgrc files between our machines.

I'm still fairly clueless when it comes to Mercurial (despite having used it for the last 4 years), so I'm struggling to understand exactly what's happening.

Is there any particular setting (either in Mecurial or TortoiseHG) that would mean a revision pulled by me results in a local "public" phase, but when pulled by my colleague results in local "draft" phase?

2
This is normally something that happens on the server; if a repository is marked as non-publishing, then pushed commits will remain in the draft phase. I don't know enough about RhodeCode, but apparently there may have been a recent issue with repositories be made non-publishing by default. Note that this is normally not harmful behavior. Why it's different for the two of you, I do not know.Reimer Behrends
Thanks @Reimer - I will continue to investigate. As you say, it's not that harmful, but I believe it still could potentially cause problems if we're not carefulfreefaller
Just to note: 1) I see "draft" phase for changesets, pulled from Git-repo in my THG 2) RhodeCode support (except Mercurial) also Git+SVN reposLazy Badger

2 Answers

1
votes

There is a setting to check:

Sometimes it may be desirable to push and pull changesets in the draft phase to share unfinished work. This can be done by setting a repository to disable publishing in its configuration file:

[phases]
publish = False

Ref: https://www.selenic.com/mercurial/hg.1.html#phases

0
votes

This must be related to RhodeCode Phases control, Please check with your super admin for versions < 3.7 if they didn't un-set "set repositories as publishing" globally, if it's 3.7+ each repository has it's own Phases control under settings -> vcs.