upstream/mercurial-mirror Files · contrib/vagrant

clean: check that there are no conflicts after...

clean: check that there are no conflicts after As noted by Pulkit, there should never be any conflicts after doing a clean update, so `hg.clean()` should never return `True`. Let's check that assertion instead to clarify the code. The callers will now get a `None` instead of a `False` returned, but that should be fine (both result in a 0 exit status). Differential Revision: https://phab.mercurial-scm.org/D7984

Martin von Zweigbergk -


            r44620:abcc82bf

default

Name	Size	Modified	Last Commit	Author
/ contrib / vagrant
README.md	Loading ...
Vagrantfile	Loading ...
provision.sh	Loading ...
run-tests.sh	Loading ...

contrib/vagrant/README.md

Run Mercurial tests with Vagrant:

$ vagrant up
$ vagrant ssh -c ./run-tests.sh

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages