# HG changeset patch # User Denis Laxalde # Date 1527066011 -7200 # Node ID f0f9139016d84332eae25c8d4801fd36d106defa # Parent 6f56ff701746fccfa1a9934c5848f4d08a2b1768 topic: use preformatted block for config snippets documentation We add :: markers, empty line and properly indent blocks where needed. diff -r 6f56ff701746 -r f0f9139016d8 hgext3rd/topic/__init__.py --- a/hgext3rd/topic/__init__.py Wed May 23 11:09:37 2018 +0200 +++ b/hgext3rd/topic/__init__.py Wed May 23 11:00:11 2018 +0200 @@ -70,6 +70,8 @@ The extensions come with an option to enforce that there is only one heads for each name in the repository at any time. +:: + [experimental] enforce-single-head = yes @@ -80,19 +82,22 @@ phase usually happens on push, but it is possible to update that behavior. The server needs to have specific config for this. - # everything pushed become public (the default) - [phase] - publish = yes + # everything pushed become public (the default):: + + [phase] + publish = yes + + # nothing push turned public:: - # nothing push turned public - [phase] - publish = no + [phase] + publish = no + + # topic branches are not published, changeset without topic are:: - # topic branches are not published, changeset without topic are - [phase] - publish = no - [experimental] - topic.publish-bare-branch = yes + [phase] + publish = no + [experimental] + topic.publish-bare-branch = yes In addition, the topic extension adds a ``--publish`` flag on :hg:`push`. When used, the pushed revisions are published if the push succeeds. It also applies diff -r 6f56ff701746 -r f0f9139016d8 tests/test-topic.t --- a/tests/test-topic.t Wed May 23 11:09:37 2018 +0200 +++ b/tests/test-topic.t Wed May 23 11:00:11 2018 +0200 @@ -82,7 +82,8 @@ The extensions come with an option to enforce that there is only one heads for each name in the repository at any time. - [experimental] enforce-single-head = yes + [experimental] + enforce-single-head = yes Publishing behavior =================== @@ -91,12 +92,22 @@ phase usually happens on push, but it is possible to update that behavior. The server needs to have specific config for this. - # everything pushed become public (the default) [phase] publish = yes + # everything pushed become public (the default): + + [phase] + publish = yes + + # nothing push turned public: - # nothing push turned public [phase] publish = no + [phase] + publish = no + + # topic branches are not published, changeset without topic are: - # topic branches are not published, changeset without topic are [phase] - publish = no [experimental] topic.publish-bare-branch = yes + [phase] + publish = no + [experimental] + topic.publish-bare-branch = yes In addition, the topic extension adds a "--publish" flag on 'hg push'. When used, the pushed revisions are published if the push succeeds. It also applies