Menu
I'm new to GitHub. When I clicked a Wiki link a new Wiki was created for my repo. But I don't really need it. If I try to delete its only page, GitHub asks: "Are you sure you want to delete this page?". And I confirm that. And nothing happens, the page is still there. I can't say it's too annoying, but I'd like to know if there is a way to delete Wiki.
752
On GitHub.com, navigate to the main page of the repository. Under your repository name, click Settings . Under Danger Zone, click Delete this repository . Read the warnings. To verify that you're deleting the correct repository, type the name of the repository you want to delete. Click I understand the consequences, delete this repository.
To Delete the Wiki's "Home" page, do the following Steps: Rename "Home" to anything else. It seems that GitHub considers "Home" to be the default page and hence the "Delete" button disappears. Click on "Edit Page". Or Navigate to Edit Mode And now you can see the "Delete" button.
On GitHub.com, navigate to the main page of the repository. Under your repository name, click Settings . Under Danger Zone, click Delete this repository . Read the warnings. To verify that you're deleting the correct repository, type the name of the repository you want to delete.
Deleting a private repository will delete all forks of the repository. Some deleted repositories can be restored within 90 days of deletion. For more information, see " Restoring a deleted repository ." On GitHub.com, navigate to the main page of the repository.
Click on the Settings button on the GitHub page of your project and uncheck Wikis.
It should disappear.
151
The missing bits are on GitHub as always. Combined with the usual git-fu you can erase all data on a GitHub repo, for example destroy a wiki ACCOUNT/REPO.wiki.git:
git clone [email protected]:ACCOUNT/REPO.wiki.git cd REPO.wiki git checkout --orphan empty git rm --cached -r . git commit --allow-empty -m 'wiki deleted' git push origin empty:master --force Warning! This recipe allows to really destroy all data (on any repo) on GitHub, except for what may be still cached somewhere. My test shows that even
git clone --mirror [email protected]:ACCOUNT/REPO.wiki.git cannot bring back any trace of old data afterwards. BTW learning to understand what above does is a good exercise in learning git ;)
21
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
