hg push -b branchname --completed-tasks pushes incomplete tasks
This might related to
#27. The scenario I encountered was 2 branches (default and unstable) with outgoing changesets on both. I did not want to push the changesets on default, just unstable. Additionally, unstable has 1 incomplete task and many new tasks.
From unstable, "hg push -b unstable" complained of incomplete tasks. Good. Next "hg push -b unstable --complete-tasks" complained that remote heads would be created. Not so good. Additionally, "hg push -r 97" failed with "abort: unknown branch '97'". I had to disable tasks so I could push the desired change sets manually.
I'll try to get a proper test scenario up in the next week or two.