Impossible to know why a branch cannot be merged

Bug #1443481 reported by Steve Dodier-Lazaro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

Sometimes it's not possible to use a branch for a merge proposal, albeit I still don't understand why. For instance, I can't make a merge proposal from a branch in ~name/+junk/. I also can't seem to merge a svn-imported branch into a bzr branch. There might be other cases I yet have to discover.

Now onto the bug. When impossible to merge, Launchpad simply makes the "Propose for merge" link disappear, leaving the user to guessing why the action can't be performed. If I don't know why I cannot merge, then I don't know what to do to my branch to make it merge-able, or whether I should use another tool.

Therefore, could you please re-add the "Propose for merge" link when a merge is impossible, but grey it out and add a unique error message for each condition that prevents a branch from being used in a merge proposal?

Thanks,

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.