Re: Linking Patchwork with Sashiko?

[Mauro Carvalho Chehab <mchehab+huawei@kernel.org>]

On Thu, 4 Jun 2026 08:52:01 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:

> On Wed, 3 Jun 2026 09:50:06 +1000
> Matthieu Baerts <matttbe@kernel.org> wrote:
> 
> > Hi Mauro, Derek, Roman,
> > 
> > On 03/06/2026 06:39, Mauro Carvalho Chehab wrote:  
> > > On Tue, 02 Jun 2026 20:13:15 +0000
> > > Roman Gushchin <roman.gushchin@linux.dev> wrote:    
> > >> Derek Barbosa <debarbos@redhat.com> writes:    
> > >>> On Sat, May 30, 2026 at 08:53:51PM +0200, Mauro Carvalho Chehab wrote:      
> > 
> > (...)
> >   
> > >>> - pw_tools is a workaround solution to get/set status on patchwork via bot-mail
> > >>>   parsing. pw tokens also have broad permission scope.
> > >>>
> > >>> which that leaves us with two "methods" of integration:
> > >>>
> > >>> 1. The Sashiko daemon calls the pw_tools script directly to update the status.
> > >>> 2. Sashiko sends a single-per-patch-email with parseable "status" to a mailing
> > >>> list, where some running daemon will pickup the mail.      
> > >>
> > >> This feels a bit hacky.    
> > > 
> > > The alternative that would be acceptable, at least on media, is if 
> > > one would add support on patchwork to have a separate permission just
> > > for checks update.    
> > 
> > Indeed. It looks like there is an old feature request about that:
> > 
> >   https://github.com/getpatchwork/patchwork/issues/14
> > 
> > Linked to Mauro's email from Dec 2015 :)  
> 
> If it is OK to have a global CI permission, I think this patch
> would do the trick (currently untested):

Added both global and per-project permissions to add CI checks:

	https://github.com/getpatchwork/patchwork/pull/653

Tested on a docker container created on the top of current
upstream, with the database imported from linuxtv.org and
migrated to the new permissions model.

Regards,
Mauro

Thanks,
Mauro