b4 prep --show-info for non-current branch

b4 prep --show-info for non-current branch

[Mark Brown]

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

Hi Konstantin,

I'm now using b4 prep --show-info in my scripting.  Something that would
be really useful would be being able to pass in a branch name to query
information from, so I can do things like push serieses through my CI
without actually having to be on the branch.

Thanks,
Mark

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

Re: b4 prep --show-info for non-current branch

[Konstantin Ryabitsev]

On Tue, Dec 27, 2022 at 05:10:06PM +0000, Mark Brown wrote:
> Hi Konstantin,
> 
> I'm now using b4 prep --show-info in my scripting.  Something that would
> be really useful would be being able to pass in a branch name to query
> information from, so I can do things like push serieses through my CI
> without actually having to be on the branch.

I poked at it a bit, but doing it properly will require a bit of refactoring,
because a lot of internal commands will need to be modified. In general, I'm
probably going to make this a larger effort -- some commands already accept
--gitdir and --branch parameters (e.g. b4 ty), so it makes sense to make these
flags understood globally instead of per-command. 

Once that work is done, you should be able to run something like:

    b4 [-g path/to/somerepo] [-b b4/some-branch] prep --show-info

-K

Re: b4 prep --show-info for non-current branch

[Mark Brown]

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

On Wed, Jan 04, 2023 at 02:50:02PM -0500, Konstantin Ryabitsev wrote:
> On Tue, Dec 27, 2022 at 05:10:06PM +0000, Mark Brown wrote:

> > I'm now using b4 prep --show-info in my scripting.  Something that would
> > be really useful would be being able to pass in a branch name to query
> > information from, so I can do things like push serieses through my CI
> > without actually having to be on the branch.

> I poked at it a bit, but doing it properly will require a bit of refactoring,
> because a lot of internal commands will need to be modified. In general, I'm
> probably going to make this a larger effort -- some commands already accept
> --gitdir and --branch parameters (e.g. b4 ty), so it makes sense to make these
> flags understood globally instead of per-command. 

> Once that work is done, you should be able to run something like:

>     b4 [-g path/to/somerepo] [-b b4/some-branch] prep --show-info

Thanks - that makes sense and would more than meet my needs.

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