support 'bzr push bug:lp:1234'

[Robert Collins]

 affects bzr
 status confirmed
 importance medium
 done

This would lookup the product the bug is on, if there is more than one,
ask, and generate a branch just for the bug.

I have in my head that this would be bug tracker connected, so that
other trackers can be used too.

I don't plan to do this, but it would be very useful.

-Rob

[Martin Pool (mbp)]

If you don't know which product the branch is on, how did you get a branch in the first place?

So this is meant to handle things like: I have a fix for bug 123 in my trivial branch, and I want to push just that fix to lp:~mbp/bzr/123 but I don't want to spell that out?

[Robert Collins (lifeless)]

On Mon, 2009-12-14 at 02:15 +0000, Martin Pool wrote:
> If you don't know which product the branch is on, how did you get a
> branch in the first place?
>
> So this is meant to handle things like: I have a fix for bug 123 in my
> trivial branch, and I want to push just that fix to lp:~mbp/bzr/123 but
> I don't want to spell that out?

Yes

[Gordon Tyler (doxxx)]

I'd say this is predicated on integration of launchpadlib into the launchpad plugin or otherwise improving the launchpad plugin to be able to make the correct webservice calls to find the associated project of the parent branch. Unless you just want to parse the parent branch URL...

[Jonathan Lange (jml)]

I have a related case. I'd like to have a plugin that lets me do something like:

$ bzr fix lp:1241325

And then results in a new local branch that has a useful name ending with the bug number, the branch being pushed and linked to the Launchpad bug, and the bug being marked "In progress" and assigned to me.

I might file a separate bug for this, or I might JFDI.