Opened 5 years ago
Last modified 4 years ago
#8130 open enhancement
Patchwork accepted marks, where are they?
| Reported by: | Balling | Owned by: | |
|---|---|---|---|
| Priority: | wish | Component: | undetermined |
| Version: | unspecified | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description (last modified by )
Can you automate accepted marks on patchwork and recheck all old patches (some hashes comparison with master branch, maybe)? Because as of now this is very uncomfortable. I need to compare with github repo if the patch is there, etc. E.g. https://patchwork.ffmpeg.org/patch/14523/
6b22e28f4c857b2d9c045001add083343f506d84
Change History (4)
comment:1 by , 5 years ago
| Status: | new → open |
|---|
follow-up: 3 comment:2 by , 5 years ago
| Component: | website → undetermined |
|---|---|
| Description: | modified (diff) |
| Priority: | normal → wish |
| Type: | task → enhancement |
comment:3 by , 5 years ago
Replying to cehoyos:
Hey, I will even give you documentation link https://github.com/getpatchwork/patchwork/blob/8837251ae03602af6818470e31540331cef7460e/docs/deployment/installation.rst#optional-configure-your-vcs-to-automatically-update-patches
comment:4 by , 4 years ago
https://patchwork.ffmpeg.org/comment/56183/
Nice, finally!
a lot of patchwork patch maintaince can be automated, ive written a script
to do that.
What this does is basically look at local git, fetch all patches from patchwork
(and cache them locally)
and then find stuff which is either invalid, superseeded, applied, ... but not
marked correctly
last it dumps the command line commands to the screen for a human to decide
if they are correct and should be run as is or not.
See:
https://github.com/michaelni/patchwork-update-bot
So... Mmm. Maybe you can do that? Or I will close this.