Automatically mark merge proposals when possible

[Daniel Schierbeck]

When the are no unmerged revisions in a merge proposal, it should be marked as merged.

[Tim Penhey (thumper)]

Now this is somewhat contentious.

What about the situation where a user creates a new hosted branch in Launchpad, proposes for merging on trunk, and then intends to start work on it.

We don't want to mark it merged before it has even been started.

[Daniel Schierbeck (dasch)]

Could it be checked whether there are any commits in the new branch at all? This could be tricky.

It would probably also be a good idea to disallow proposing "empty" branches for merging.

[Jonathan Lange (jml)]

There's a better way of implementing this: check for a revision which actually merges the branches -- this avoids the 'empty branch' problem.

I don't think that the feature is at all contentious, I think it's highly desirable.

[Tim Penhey (thumper)]

Fixed in RF 7104.

[Elliot Murphy (statik)]

Thank you, this is awesome, will make my life much easier.