If I fork repository joe/foo
, and it has a Wiki, I won\'t get the wiki. Right now I\'m just interested in forking the wiki to add pages to it.
You are able to just clone a Wiki from a repo now. You can find a tab called Git Access
under Wiki
tab of a repo.
But you still can not fork a wiki without forking its project repo.
As of 30 March 2016, you can just create a new "Home" Wiki page and the wiki pages for the forked repository will show up in your fork once the new Home page is created (provided that you have forked the parent repository).
In June 2019, here's how I did that:
git clone https://github.com/org-a/project-x.wiki.git
https://github.com/org-b/project-x
, add the new remote to the wiki repo: git remote add fork https://github.com/org-b/project-x.wiki.git
git push -f fork master
Great. Now you have forked a repo and its wiki.
(By the way, Github should do this automatically, right?)
You can't fork it directly on GitHub, but you can get Git access to it by going into the Git access tab of the wiki and you should be able to fork it on your local machine and edit it as much as you want (and even get updates to it!)
If you're making your own wiki that others would be interested in forking, you could do something like we did for the RailsConf 2012 wiki.
We made a local clone of the wiki and then did git push --force
to the "code" repository. It gets a little out of sync, but that's easy to rectify.