We have some amount of trivial mediawiki-config changes that don't really need to be babysat through a SWAT deploy.

Things like adding copy upload domains, can be verified by a person (is the URL correct? is it being added to the correct place? is it syntactically valid (though, jerkins should be telling us that)), and don't need testing on an mwdebug* box, nor do they need the patch owner to be around for deploying them, which, in some cases is a blocker for people being able to get them deployed. They shouldn't have to have to find someone who will "look after it".

Similarly, we get mediawiki-config changes that get pushed to gerrit, and never get merged/deployed even though they may have received appropriate CR+1.

SWAT works for many types of patches, but it doesn't seem relevant to other types. We should find a way to enable these patches to go out again in a more timely, and potentially uploader unattended, fashion

Historically, I would on a semi regular basis, go through and merge a lot of these patches and deploy them thereafter.