review-tui: Handle different Patchwork current statuses

review-tui: Handle different Patchwork current statuses

[Krzysztof Kozlowski]

Hey,

I am trying to adapt b4 review to DT workflow with DT patchwork and I
think interpretation of current patch status needs customization. I have
in .gitconfig:

[b4]
	pw-review-state = needs-ack
	pw-accept-state = not-applicable
	pw-discard-state = changes-requested

But b4 review tui in Patchwork status does not show any patches under
Needs ACK.

https://patchwork.kernel.org/project/devicetree/list/

To recap, our statuses are used like:
0. "New": not processed by any automation
1. "Under Review": being processed by automation
2. "Needs ACK": Actually waiting for our review or being reviewed. This
is what we want to see in list of patches.
3. "Changes requested": Patch rejected with changes needed
4. "Not applicable": Patch was reviewed but handled elsewhere as most of
work is like that.

Either I miss some .gitconfig options or b4 is missing such
customization. If the latter, can you add a feature-request for this? I
would like to adopt b4 and move away from our internal scripting...


Best regards,
Krzysztof

Re: review-tui: Handle different Patchwork current statuses

[Krzysztof Kozlowski]

On 24/09/2026 14:52, Krzysztof Kozlowski wrote:
> Hey,
> 
> I am trying to adapt b4 review to DT workflow with DT patchwork and I
> think interpretation of current patch status needs customization. I have
> in .gitconfig:
> 
> [b4]
> 	pw-review-state = needs-ack
> 	pw-accept-state = not-applicable
> 	pw-discard-state = changes-requested
> 
> But b4 review tui in Patchwork status does not show any patches under
> Needs ACK.
> 
> https://patchwork.kernel.org/project/devicetree/list/
> 
> To recap, our statuses are used like:
> 0. "New": not processed by any automation
> 1. "Under Review": being processed by automation
> 2. "Needs ACK": Actually waiting for our review or being reviewed. This
> is what we want to see in list of patches.
> 3. "Changes requested": Patch rejected with changes needed
> 4. "Not applicable": Patch was reviewed but handled elsewhere as most of
> work is like that.
> 
> Either I miss some .gitconfig options or b4 is missing such
> customization. If the latter, can you add a feature-request for this? I
> would like to adopt b4 and move away from our internal scripting...
> 

Ah, and if that matters: b4 v0.16.0

Best regards,
Krzysztof