[Bug Infrastructure/30997] New: Automate patchwork committed marking

[Bug Infrastructure/30997] New: Automate patchwork committed marking

[mark at klomp dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30997

            Bug ID: 30997
           Summary: Automate patchwork committed marking
           Product: sourceware
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Infrastructure
          Assignee: overseers at sourceware dot org
          Reporter: mark at klomp dot org
  Target Milestone: ---

Currently individuals run scripts by hand to close patches (mark them as
committed). This could be automated by running these scripts from a git hook or
from builder when a patch is committed.

https://patchwork.readthedocs.io/en/latest/deployment/installation/#optional-configure-your-vcs-to-automatically-update-patches

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug Infrastructure/30997] Automate patchwork committed marking

[siddhesh at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30997

Siddhesh Poyarekar <siddhesh at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |siddhesh at sourceware dot org

--- Comment #1 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
FWIW, I run it as a cron job from my sourceware shell account.  I suppose it
could be trivially done for all projects that use patchwork from a single such
account.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug Infrastructure/30997] Automate patchwork committed marking

[carlos at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=30997

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com

--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> ---
I strongly recommend against it being a git hook since the hook involves
potentially complex code running on the git server, and the process need only
reach *eventual consistency* over time to support review of the patches in the
queue. Just like with an MR/PR workflow someone might commit a similar fix
ahead of you, and we'll never be able to keep the queue 100% automatically
clear.

My suggestion would be to write a bot that is run in a cron job as part of
patchwork.sourceware.org process automation, and that the bot account should
have maintainer status on all the projects and close the patches as committed.

As an evolving solution I would just have Siddhesh turn this on for all the
projects. I suggest a patchwork bot account to be used so it can be identified
more easily e.g. autoclose-bot.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug Infrastructure/30997] Automate patchwork committed marking

[mark at klomp dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30997

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://sourceware.org/bugz
                   |                            |illa/show_bug.cgi?id=30042

-- 
You are receiving this mail because:
You are the assignee for the bug.