prev: respect `commands.update.check` config option in `hg prev` (issue5808) `commands.update.check` config option determines what level of checking should be done when we update to another revision. When we set this config option to `noconflict`, it updates your working directory to a specified revision only when there will be no conflicts which is a very nice behavior. This patch adds logic to respect the config option so that we can have that nice behavior with `hg prev` too. It turns out, we just needed to use hg.updatetotally() and add some cases to check config option. Right now, we only respect the config if value is set to `noconflict`. Otherwise we fallback to the default behavior. This is a part of fixing issue5808. Test changes demonstrate the fix.

     1

#require test-repo

     2

     3

Enable obsolescence to avoid the warning issue when obsmarker are found

     4

     5

  $ cat << EOF >> $HGRCPATH

     6

  > [diff]

     7

  > git = yes

     8

  > [experimental]

     9

  > evolution=all

    10

  > EOF

    11

    12

Go back in the hg repo

    13

    14

  $ cd $TESTDIR/..

    15

    16

  $ for node in `hg log --rev 'not public() and ::. and not desc("# no-check-commit")' --template '{node|short}\n'`; do

    17

  >    hg export $node | ${RUNTESTDIR}/../contrib/check-commit > ${TESTTMP}/check-commit.out

    18

  >    if [ $? -ne 0 ]; then

    19

  >        echo "Revision $node does not comply with rules"

    20

  >        echo '------------------------------------------------------'

    21

  >        cat ${TESTTMP}/check-commit.out

    22

  >        echo

    23

  >   fi

    24

  > done