view contrib/hammerclient.py @ 5884:21a8f0336f26 stable

next: treat targets that need evolution the same as regular targets Unless --no-evolve is given. In case when there's only one stable child that otherwise fits perfectly as a hg next target, but there are also unstable children on the current topic and we are allowed to evolve them, hg next should treat them as targets too and give a prompt to select the revision to update to. With this patch it does.
author Anton Shestakov <av6@dwimlabs.net>
date Thu, 22 Apr 2021 17:19:01 +0800
parents f97379faefa3
children
line wrap: on
line source

#!/usr/bin/env python
import os
import sys
import subprocess

if len(sys.argv) < 2:
    execname = os.path.basename(sys.argv[0])
    sys.stderr.write("usage: %s CLIENT_ID\n" % execname)

client_id = sys.argv[1]

subprocess.check_call(['hg', 'branch', "--force", "hammer-branch-%s" % client_id])

while True:
    subprocess.check_call([
        'hg', 'commit',
        "--config", "ui.allowemptycommit=yes",
        "--message", "hammer-%s" % client_id,
    ])
    nodeid = subprocess.check_output([
        'hg', 'log', '--rev', '.', '--template', '{node}'
    ])
    subprocess.check_call([
        'hg', 'debugobsolete', ''.join(reversed(nodeid)), nodeid
    ])
    subprocess.check_call(['hg', 'pull'])
    subprocess.check_call(['hg', 'push', '--force'])