search

mricon / b4

Tool to help with email-based patch workflows
GNU General Public License v2.0
59 stars 20 forks source link

Explicit patchwork integration #22

Open rossburton opened 6 months ago

rossburton commented 6 months ago

I'd like the ability to explicitly interact with patchwork from b4, without it being implicit in am/ty calls.

For example, I'm picking patches from the mail to build a branch for review. Just because I've am'd a patch doesn't mean that I want to set it as Under Review in patchwork straight away, as I may look at it and decide to look later.

My ideal workflow would be something like repeated b4 shazam calls to build a branch, which I can then review by eye, build test, pass to automated build testing, etc. At that point I'd like to mark all of the patches in my branch as Under Review (or whatever state I desire) in patchwork.

I may need to drop patches during this testing and explicitly mark them as rejected.

Also when the branch has passed testing, I'd like to be able to mark all of the remaining patches as Reviewed or similar in patchwork.

mricon commented 6 months ago

I think this level of integration is beyond the scope of b4. Have you tried using pwclient (https://patchwork.readthedocs.io/projects/pwclient/)?