User:MusikBot/PermClerk

PermClerk

Bot clerking at requests for permissions.

Y Enabled

To disable, set /Run to anything other than true (link)

Errors are logged at /Error log

Human-readable report

No errors! Report generated at 13:50, 27 July 2024 (UTC)

All requests are archived at Wikipedia:Requests for permissions/Archive as approved or denied. This is done as a historical reference, namely so that admins can review previously declined requests.

N hours after the last comment was made on a request (as specified in the config), the discussion is removed from that page and an entry containing a PermaLink to the discussion is added to the archives, noting the user and the permission.

{{User:MusikBot/override}} can be used to override any other {{done}} or {{not done}} templates, and make the bot ignore the user's rights. For example, you may use {{done}}{{User:MusikBot/override|d}} when a user has requested revocation of a user right (marking as done and forcing to archive as done).

You can also force immediate archiving of a request with {{User:MusikBot/archivenow}} ~~~~

Removes extraneous headers and repairs malformed requests. This functionality is not configurable, but it can be turned off entirely.

Updates {{WP:PERM/Backlog}} based on configurable conditions. At the time of writing, this is set to 3+ requests or any request over 7 days old.

Marks requests as {{already done}} if the user already has the permission they are requesting. Only runs on WP:PERM/C and WP:PERM/AWB. For other PERM pages, the bot will wait N hours after the request (see config) has been made before concluding the admin forgot to mark the request as {{done}}.

Searches the declined archives and comments if the user has had any relevant requests recently declined, with permalinks to the relevant page. Does not run on WP:PERM/C. The number of days back the bot should search is configurable.

Comments if the user does not meet the configurable qualifications for that permission. The data is kept up-to-date until the request is responded to.

If the user does not meet one of the prerequisites, the bot will comment with the relevant data. For instance, if 200 mainspace edits are required, the bot will comment "this user has made X edits to the mainspace". If multiple requirements are not met, a single humanized sentence is constructed, as opposed to making multiple comments.

These prerequisites do not necessarily represent a hard requirement, and the comments made by the bot are purely for convenience.

Comments if the user has had the requested permission revoked in the past N days, as specified in the config.

Functionality can be tweaked at /config. Configuration data is in the form of JSON.

IMPORTANT:

• Do not modify the config files unless you have a basic understanding of JSON
• Read the documentation first.
• Do not change the key values.
• Keys should always be strings, e.g. use "option": true instead of option: true.
• Strings should be wrapped in double-quotes, e.g. "option" instead of 'option'.
• Boolean values must be either true or false with no quotations around it.
• Numerical values must be integers with no quotations around it.
• The last key/value pair within a hash or the value value in an array must not have a comma at the end of it
• Essentially if the JSON editor interface says there are any syntax errors or warnings, you have done something wrong