view hgweb.cgi @ 42703:073cfff9aaef

unshelve: delete shelvedstate after a successful unshelve --continue

`unshelve --continue` was preventing the deletion of `shelvedstate` on
a partial `unshelve`. Ideally, `shelvedstate` should be deleted after
a successful `unshelve`. Now, the behavior of `unshelve --continue`
will be as follows in interactive mode:

1] The user tried to `unshelve` changes interactively but, ran into
 conflicts.
2] They resolved the conflicts and triggered `unshelve --continue`
 but, unshelved changes partially.
3] Now, on trying to do `unshelve --continue` again will abort as
 the last `unshelve` was successful and we are deleting the
 `shelvedstate`.
4] If they want to unshelve the remaining shelved change, they
 need to trigger `unshelve` without `--continue`.

Differential Revision: https://phab.mercurial-scm.org/D6694

#!/usr/bin/env python
#
# An example hgweb CGI script, edit as necessary
# See also https://mercurial-scm.org/wiki/PublishingRepositories

# Path to repo or hgweb config to serve (see 'hg help hgweb')
config = "/path/to/repo/or/config"

# Uncomment and adjust if Mercurial is not installed system-wide
# (consult "installed modules" path from 'hg debuginstall'):
#import sys; sys.path.insert(0, "/path/to/python/lib")

# Uncomment to send python tracebacks to the browser if an error occurs:
#import cgitb; cgitb.enable()

from mercurial import demandimport; demandimport.enable()
from mercurial.hgweb import hgweb, wsgicgi
application = hgweb(config)
wsgicgi.launch(application)