diff mercurial/help/config.txt @ 29413:31d3ab7985b8

ui: path option to declare which revisions to push by default Now that we have a mechanism for declaring path sub-options, we can start to pile on features! Many power users have expressed frustration that bare `hg push` attempts to push all local revisions to the remote. This patch introduces the "pushrev" path sub-option to control which revisions are pushed when no "-r" argument is specified. The value of this sub-option is a revset, naturally. A future feature addition could potentially introduce a "pushnames" sub-options that declares the list of names (branches, bookmarks, topics, etc) to push by default. The entire "what to push by default" feature should probably be considered before this patch lands.
author Gregory Szorc <gregory.szorc@gmail.com>
date Sun, 26 Jun 2016 07:59:02 -0700
parents ecc9b788fd69
children fd93b15b5c30
line wrap: on
line diff
--- a/mercurial/help/config.txt	Sat Jun 25 18:35:14 2016 -0700
+++ b/mercurial/help/config.txt	Sun Jun 26 07:59:02 2016 -0700
@@ -1282,6 +1282,18 @@
    The URL to use for push operations. If not defined, the location
    defined by the path's main entry is used.
 
+``pushrev``
+   A revset defining which revisions to push by default.
+
+   When :hg:`push` is executed without a ``-r`` argument, the revset
+   defined by this sub-option is evaluated to determine what to push.
+
+   For example, a value of ``.`` will push the working directory's
+   revision by default.
+
+   Revsets specifying bookmarks will not result in the bookmark being
+   pushed.
+
 The following special named paths exist:
 
 ``default``