phabricator: restack any new orphans created by phabsend (issue6045) Previously, posting a new review for a non head commit would orphan the head. The general case is any descendant of the selected revisions got orphaned if this was the first time the selected revisions were submitted. It doesn't happen when resubmitting. I've already had coworkers hit this a few times and get confused. Since posting a review isn't generally thought of as an editing operation, it would probably be easier for new users if we just restacked. This avoids restacking existing orphans around the submission because that may involve merge conflict resolution. Users who already have orphans should know how to stabilize them anyway. Differential Revision: https://phab.mercurial-scm.org/D8438

     1

# Balto (https://bitbucket.org/lothiraldan/balto/src) is a test orchestrator

     2

# which is compatible with all test runner that can emit the LITF

     3

# (https://github.com/lothiraldan/litf) test format.

     4

     5

# The plugin for the Mercurial test runner is mercurial-litf

     6

# (https://pypi.org/project/mercurial-litf/). Make sure to follow the

     7

# instruction and configuration instructions here:

     8

# https://bitbucket.org/lothiraldan/mercurial_litf/src/default/

     9

    10

# You can launch Balto with `balto /path/to/mercurial/tests/`

    11

    12

name = "Mercurial Test Suite"

    13

tool = "mercurial"