Bug 30997 - Automate patchwork committed marking
Summary: Automate patchwork committed marking
Status: NEW
Alias: None
Product: sourceware
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: overseers mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-24 09:49 UTC by Mark Wielaard
Modified: 2024-03-24 22:02 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Wielaard 2023-10-24 09:49:02 UTC
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
Comment 1 Siddhesh Poyarekar 2023-10-24 10:20:31 UTC
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.
Comment 2 Carlos O'Donell 2023-10-24 12:30:24 UTC
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.