@Reception123 Can you fix the typo in my username in your original post?

Also, I'm attaching a link to the original Miraheze Phabricator ticket, which may provide additional information.

User-RhinosF1

@Reception123: Following https://www.mediawiki.org/wiki/How_to_report_a_bug to provide a list of clear steps to reproduce (step by step, as a list), then what you expect, and what happens instead, would increase chances that someone would take a look into this. Please structure your bug reports - thanks.

In T259265#6914394, @Aklapper wrote:

@Reception123: Following https://www.mediawiki.org/wiki/How_to_report_a_bug to provide a list of clear steps to reproduce (step by step, as a list), then what you expect, and what happens instead, would increase chances that someone would take a look into this. Please structure your bug reports - thanks.

@Aklapper Oh yeah, I requested this, and @Reception123 created the upstream task for me. The issue is with the rebuildAll.php maintenance script, which automatically marks revisions as unpatrolled. It may not just be former administrators, though, but it seems like only certain previously patrolled (autopatrolled or manual, even) are now marked as unpatrolled. I'm just not sure I understand the workflow for that script, though, so unsure if specifically a bug but rather an undesirable feature in the maintenance script.

I would say the steps to produce are as follows:

1. Grant a user the sysop permission
2. Have the new sysop user create a few revisions
3. Remove the the sysop permission from the user
4. Run rebuildAll.php on the given wiki, with the default/recommended parameters specified/not specified (whatever the default is, I think)
5. Review the former sysop's recent revisions and note that the revisions are now unpatrolled

If this is not a bug, can we not add a feature request to rebuildAll.php that would add a parameter to set the rc_patrol indicator to the value specified in the parameter the system administrator issues?