b4 pr fetch refuses to fetch already fetched branches

b4 pr fetch refuses to fetch already fetched branches

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

Hi,

Running b4 pr on a message that mentions a commit that's already in some
local branch nor (AFAICT) sets up to do a b4 ty for the PR (which is a
large part of what I'm looking for here):

$ b4 pr 87jythopgp.fsf@bootlin.com 
Looking up 87jythopgp.fsf@bootlin.com
Looking at: [GIT PULL] spi-nand/spi-mem changes for 7.2
Pull request tip commit exists in the following branches:
  b4/review/20260216-sc2730-regulators-13ba789641a4
  b4/review/20260527-spi-cadence-quadspi-add-phy-tuning-support-bcef16741d7d
  b4/review/20260528-asoc-use-named-initializers-for-platform_device_id-arrays-b0874c719b61

(the fact that b4 pr will happily pick up random linux-next commits as
branch bases is a separate issue...).  The fact that I've got a copy of
the branch locally shouldn't be relevant to my descision to pull it into
a published branch.

Thanks,
Mark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: b4 pr fetch refuses to fetch already fetched branches

[Konstantin Ryabitsev]

On Fri, Jun 12, 2026 at 01:58:54PM +0100, Mark Brown wrote:
> Hi,
> 
> Running b4 pr on a message that mentions a commit that's already in some
> local branch nor (AFAICT) sets up to do a b4 ty for the PR (which is a
> large part of what I'm looking for here):

You're right, this behaviour was not very useful. I've pushed (really!) a
change that should make the checks more narrow and only bail if the PR is
already in the current branch (or the one specified with -b). Even after it
bails, the PR info will be recorded, so you can run b4 ty post-fact.

-K

Re: b4 pr fetch refuses to fetch already fetched branches

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

On Fri, Jun 12, 2026 at 04:32:13PM -0400, Konstantin Ryabitsev wrote:
> On Fri, Jun 12, 2026 at 01:58:54PM +0100, Mark Brown wrote:

> > Running b4 pr on a message that mentions a commit that's already in some
> > local branch nor (AFAICT) sets up to do a b4 ty for the PR (which is a
> > large part of what I'm looking for here):

> You're right, this behaviour was not very useful. I've pushed (really!) a
> change that should make the checks more narrow and only bail if the PR is
> already in the current branch (or the one specified with -b). Even after it
> bails, the PR info will be recorded, so you can run b4 ty post-fact.

Thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]