New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archiving repositories #477
Comments
Is there a built-in way to archive a repository through GitHub? |
Yes. (https://help.github.com/articles/archiving-a-github-repository/ https://help.github.com/articles/archiving-repositories/ etc) If archiving is preferred to deleting, I'm fine with that too |
I'd rather that just to preserve backlinks and other traces where we might have linked to stuff in the past. |
Archived LocalSettings and extensions as they're both deprecated repositories. Waiting to hear if anyone else has thoughts on archiving other repositories before proceeding. |
I was thinking of blanking the skin + extension repos so that just in case there's people who are using those, are forced to use whatever we provide as the replacement in the README instead. (e.g Brickimedia/Refreshed should provide a link to wikimedia/mediawiki-skins-Refreshed, Brickimedia/Snippet provides a link to wikimedia/mediawiki-extensions-TextExtracts). Thoughts on that? |
Would it be possible for us to turn Brickimedia/Refreshed into a mirror of wikimedia/mediawiki-skins-Refreshed? |
After some looking, apparently that's possible (didn't know that till now). Here's the link (which contains 3 different sections): https://help.github.com/articles/duplicating-a-repository/ |
Making this ticket after a ping in Brickimedia/splash@ea75cbb (thanks for the ping!)
We'll probably be fine with deleting most of them or all of them. Here are some reasons why:
Pinging for @georgebarnick and @mary-kate for thoughts on this.
The text was updated successfully, but these errors were encountered: