Topic: update mispelled tag

The bulk update request #12007 is pending approval.

mass update nokull_(riggedreded) -> nokrull_(riggedreded)

Reason: it seems i mispelled the tag once and made a whole new one my apologies

Wouldn't an alias be more appropriate so that this can't happen again?

heartstoppa said:
Wouldn't an alias be more appropriate so that this can't happen again?

Not always necessary. Updating or manual changes can be done if it's a relatively rare typo/obscure tag.

regsmutt said:
Not always necessary. Updating or manual changes can be done if it's a relatively rare typo/obscure tag.

Well, since the manual update has already been done, this BUR is now useless.

faucet said:
Well, since the manual update has already been done, this BUR is now useless.

faucet's right.

To elaborate for the uninitiated, as there are zero posts tagged w/ nokull_(riggedreded); a mass update won't do anything. I think nuking the tag (which seems to be admin only btw) would delete it, but seeing as there's only 16 posts with the later, I'd say just don't worry about & make sure you use the right one.

We typically don't bother with AIBURs (Ailases Implications, & Bulk Update Requests) when there's less than 20 affected posts; if there's not that many, than just manually correcting the tag is likely sufficient. We don't want to incur the overhead of AIBURs when no one's using the incorrect dead tag.

Edit: it wouldn't, ty Donovan

aacafah said:
I think nuking the tag (which seems to be admin only btw) would delete it

The nuke command can indeed only be used in BURs created by admins, and it just removes the tag from all posts it's on
https://github.com/e621ng/e621ng/blob/837642ec58d98a57d00a8a17c17458bec25895a3/app/logical/bulk_update_request_importer.rb#L238
https://github.com/e621ng/e621ng/blob/837642ec58d98a57d00a8a17c17458bec25895a3/app/jobs/tag_nuke_job.rb