>>! In T189594#4073872, @Krinkle wrote:
> @Ladsgroup That seems fine, but it might also make sense for this to be more re-usable and less manual/error-prone work. For example, we could have a maintenance script that goes through logging/patrol/patrol<2017 (as you mentioned) but instead of deleting things, it could `SET log_action='autopatrol'` for the ones it finds.
> Then once that's done, we can run the autopatorl-purge script without any special parameters.
> * The purge script will only need to focus on autopatrol.
> * We'll be able to re-use it for (eventually, low-priority) correcting older logs on other wikis to provide filtering and separation of patrol vs autopatrol.
> * We'll be able to re-use it when we want to do purging on another wiki in the future. (Without manual queries and deletion.)
> * It'll be usable by third-parties.
> * We could even add the patrol-marker script to the installer by default to run once on upgrades, so that small/third-party wikis will have all old autopatrol records properly marked as such.