ui: support declaring path push urls as sub-options Power users often want to apply per-path configuration options. For example, they may want to declare an alternate URL for push operations or declare a revset of revisions to push when `hg push` is used (as opposed to attempting to push all revisions by default). This patch establishes the use of sub-options (config options with ":" in the name) to declare additional behavior for paths. New sub-options are declared by using the new ``@ui.pathsuboption`` decorator. This decorator serves multiple purposes: * Declaring which sub-options are registered * Declaring how a sub-option maps to an attribute on ``path`` instances (this is needed to `hg paths` can render sub-options and values properly) * Validation and normalization of config options to attribute values * Allows extensions to declare new sub-options without monkeypatching * Allows extensions to overwrite built-in behavior for sub-option handling As convenient as the new option registration decorator is, extensions (and even core functionality) may still need an additional hook point to perform finalization of path instances. For example, they may wish to validate that multiple options/attributes aren't conflicting with each other. This hook point could be added later, if needed. To prove this new functionality works, we implement the "pushurl" path sub-option. This option declares the URL that `hg push` should use by default. We require that "pushurl" is an actual URL. This requirement might be controversial and could be dropped if there is opposition. However, objectors should read the complicated code in ui.path.__init__ and commands.push for resolving non-URL values before making a judgement. We also don't allow #fragment in the URLs. I intend to introduce a ":pushrev" (or similar) option to define a revset to control which revisions are pushed when "-r <rev>" isn't passed into `hg push`. This is much more powerful than #fragment and I don't think #fragment is useful enough to continue supporting. The [paths] section of the "config" help page has been updated significantly. `hg paths` has been taught to display path sub-options. The docs mention that "default-push" is now deprecated. However, there are several references to it that need to be cleaned up. A large part of this is converting more consumers to the new paths API. This will happen naturally as more path sub-options are added and more and more components need to access them.

     1

  $ hg init a

     2

     3

  $ echo a > a/a

     4

  $ hg --cwd a ci -Ama

     5

  adding a

     6

     7

  $ hg clone a c

     8

  updating to branch default

     9

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    10

    11

  $ hg clone a b

    12

  updating to branch default

    13

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    14

    15

  $ echo b >> b/a

    16

  $ hg --cwd b ci -mb

    17

    18

Push should provide a hint when both 'default' and 'default-push' not set:

    19

  $ cd c

    20

  $ hg push --config paths.default=

    21

  abort: default repository not configured!

    22

  (see the "path" section in "hg help config")

    23

  [255]

    24

    25

  $ cd ..

    26

    27

Push should push to 'default' when 'default-push' not set:

    28

    29

  $ hg --cwd b push

    30

  pushing to $TESTTMP/a (glob)

    31

  searching for changes

    32

  adding changesets

    33

  adding manifests

    34

  adding file changes

    35

  added 1 changesets with 1 changes to 1 files

    36

    37

Push should push to 'default-push' when set:

    38

    39

  $ echo '[paths]' >> b/.hg/hgrc

    40

  $ echo 'default-push = ../c' >> b/.hg/hgrc

    41

  $ hg --cwd b push

    42

  pushing to $TESTTMP/c (glob)

    43

  searching for changes

    44

  adding changesets

    45

  adding manifests

    46

  adding file changes

    47

  added 1 changesets with 1 changes to 1 files

    48

    49

Push should push to 'default-push' when 'default' is not set

    50

    51

  $ hg -q clone a push-default-only

    52

  $ cd push-default-only

    53

  $ rm .hg/hgrc

    54

    55

  $ touch foo

    56

  $ hg -q commit -A -m 'add foo'

    57

  $ hg --config paths.default-push=../a push

    58

  pushing to $TESTTMP/a (glob)

    59

  searching for changes

    60

  adding changesets

    61

  adding manifests

    62

  adding file changes

    63

  added 1 changesets with 1 changes to 1 files

    64

    65

  $ cd ..

    66

    67

Pushing to a path that isn't defined should not fall back to default

    68

    69

  $ hg --cwd b push doesnotexist

    70

  abort: repository doesnotexist does not exist!

    71

  [255]

    72

    73

:pushurl is used when defined

    74

    75

  $ hg -q clone a pushurlsource

    76

  $ hg -q clone a pushurldest

    77

  $ cd pushurlsource

    78

  $ cat > .hg/hgrc << EOF

    79

  > [paths]

    80

  > default = https://example.com/not/relevant

    81

  > default:pushurl = file://`pwd`/../pushurldest

    82

  > EOF

    83

    84

  $ touch pushurl

    85

  $ hg -q commit -A -m 'add pushurl'

    86

  $ hg push

    87

  pushing to file:/*/$TESTTMP/pushurlsource/../pushurldest (glob)

    88

  searching for changes

    89

  adding changesets

    90

  adding manifests

    91

  adding file changes

    92

  added 1 changesets with 1 changes to 1 files

    93

    94

  $ cd ..