如何在汞推入时将变更集保持在“草稿"阶段? [英] How to keep changesets in phase “draft” on hg push?

问题描述

我如何阻止Mercury将变更集置于推送操作的公开"阶段?我希望他们保持草稿".

How can I hinder mercurial from putting changesets to phase "public" on push operations? I want them to stay "draft".

我进行了很多基础和组织编辑，而推送到的存储库仅对我而言.而且必须始终更改相位是很麻烦的.

I rebase and histedit a lot, and the repository I push to is for me only. And having to change the phase all the time is a nuisance.

推荐答案

文档未明确揭示的是:

推送阶段的更改不是纯粹的本地决定. –在上载"变更集之后，客户端向服务器请求有关提交阶段的更新，并且服务器通常是告诉他们现在是公开".

The phase-change on push is not a purely local decision. – After "uploading" the changesets, the client asks the server for updates regarding the phases of the commits, and the server is usually telling that they are now "public".

因此，.hgrc-片段

[phases]
publish = False

必须放置在服务器上，这会阻止服务器上通常的相变.然后，服务器将以相同的方式报告阶段.

has to be put on the server, which inhibits the usual phase-change there. The server will then report the phases back the same way they were pushed.

Bitbucket在设置"→存储库详细信息"→阶段" 下为此提供了一个选项.

Bitbucket has an option for this under Settings → Repository details → Phases.

这篇关于如何在汞推入时将变更集保持在“草稿"阶段?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！