comparison hgext3rd/topic/__init__.py @ 6001:806bdef19f1c mercurial-5.2

test-compat: merge mercurial-5.3 into mercurial-5.2

5943:bc445a876757

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

* nothing push turned public::

    [phase]
    publish = no

* topic branches are not published, changeset without topic are::

    [phase]
    publish = no
    [experimental]
    topic.publish-bare-branch = yes

In addition, the topic extension adds a ``--publish`` flag on :hg:`push`. When

              # (first pick I could think off, update as needed
              b'log.topic': b'green_background',
              b'topic.active': b'green',
              }

__version__ = b'0.22.2.dev'

testedwith = b'4.6.2 4.7 4.8 4.9 5.0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8'
minimumhgversion = b'4.6'
buglink = b'https://bz.mercurial-scm.org/'

6001:806bdef19f1c

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)::

    [phases]
    publish = yes

* nothing push turned public::

    [phases]
    publish = no

* topic branches are not published, changeset without topic are::

    [phases]
    publish = no
    [experimental]
    topic.publish-bare-branch = yes

In addition, the topic extension adds a ``--publish`` flag on :hg:`push`. When

              # (first pick I could think off, update as needed
              b'log.topic': b'green_background',
              b'topic.active': b'green',
              }

__version__ = b'0.22.3.dev'

testedwith = b'4.6.2 4.7 4.8 4.9 5.0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8'
minimumhgversion = b'4.6'
buglink = b'https://bz.mercurial-scm.org/'