wikimedia-gadgets / twinkle

The English Wikipedia twinkle javascript helper
http://en.wikipedia.org/wiki/Wikipedia:Twinkle
Other
136 stars 151 forks source link

morebits documentation wiki is down #1919

Open NovemLinguae opened 10 months ago

NovemLinguae commented 10 months ago

Reported by Nacaru at https://en.wikipedia.org/wiki/Wikipedia_talk:Twinkle#Why_did_the_morebits_documentation_disappear%3F

morebits documentation website is down

Website link: https://github.com/wikimedia-gadgets/twinkle/wiki/morebits

Branch: gh-pages - https://github.com/wikimedia-gadgets/twinkle/tree/gh-pages

@Amorymeltzer, I hear you might have set these up originally. Any idea how to fix?

bsoyka commented 10 months ago

Fixed!! Pulled the file from https://github.com/wikimedia-gadgets/twinkle.wiki.git using Git. (That repo won't load on the GitHub web interface, but it exists. GitHub is weird sometimes.)

The file was removed on November 1, I'd assume accidentally.

NovemLinguae commented 10 months ago

Is it possible someone vandalized the github morebits wiki? https://github.com/wikimedia-gadgets/twinkle/wiki/morebits/_history

Perhaps we should turn off public access to edit it?

Someone else would probably have to do that. I don't think I have access to the settings page.

Amorymeltzer commented 10 months ago

@NovemLinguae Yeah, you just found what I was typing out. No idea at this point—I don't have access anymore, and the gh-pages thang is usually a turn on/off in the settings, so I'd have someone check that to undo whatever was done. From the history it looks like the wiki stuff was opened up? I'd suggest checking the repo settings, but no idea when it would've been set to public in the intervening years.

NovemLinguae commented 10 months ago

Hmm, looks like the wiki is fixed, but there's also a github.io site that is broken. Anyone know how to fix that?

https://wikimedia-gadgets.github.io/twinkle/Morebits.html

nardog commented 10 months ago

That's #1668.

@siddharthvp said:

This setup currently requires syncing all code changes to the gh-pages and then invoking the docs script. Not an optimal setup – ideally we should automate the whole thing (see #1405).