[repo] Automatically protect migrated pages #111
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andrewnicols
force-pushed
the
wikimediaProtect
branch
from
8d3bb99 to
76e78bf
Compare
sarjona
approved these changes
May 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit updates our package config to use the latest version of nodemw which adds support for protecting page (which I wrote).
The patch then adds protection for all migrated pages.
I have now added a (crappy looking) banner to the old pages linking to the new. Locking those pages prevents most people from changing them. We do still need to keep an eye on them (and maybe we can automate this better too) as admins can still make changes. We also have a few which have been updated since we migrated and need to check those and update the new docs too.