Thanks for passing it on. It seems on the face of it to be a really simple thing to do - simply allow the wiki to be viewed as a git repo. Obviously, there will be more to it than I can see from outside, and possible ramifications of making the change that I have not thought through, or would not be aware of, but I hope that the benefits would outweigh the downsides.
... View more
Hi, I have a project with a Wiki, and would like to allow contributions to the Wiki, without making everyone a collaborator, or allowing Public access to the wiki. It seems to me that 99% of the solution already exists, in that the wiki is a git repository, and should be amenable to all of the existing tooling. However, there seem to be a couple of hard-coded restrictions preventing this: 1. Forking a repo does not include the related wiki. 2. There is no mechanism to view the wiki repo as a standalone git repository. e.g. https://github.com/user/project.wiki.git redirects to https://github.com/user/project.wiki which results in a 404. 1. could perhaps be considered a bug, although the wiki is conceptually a separate entity to the surrounding project, as they are actually separate unrelated git repositories. Nonetheless, even forking the wiki at the same time as forking the project would still require custom user interfaces to support Wiki pull requests as opposed to Project Pull Requests. 2. Allowing the Wiki repo to be viewed and forked as a git repo in its own right would eliminate the requirement for any special casing. Conceptually, viewing the project.wiki.git repo should display it exactly as if it were a git repo as any other, and that would immediately enable Forking, Issues, Pull Requests, etc by contributors, as is already possible for any project. From an outsider's perspective, that would simply require a mapping from the URL to the actual repo, wherever it may be stored, to enable all of that functionality. At some point, it may be desirable to support forking the wiki when forking the parent project, at which time some UI decorations may be required, such as indicating the status of a page compared to the parent wiki. e.g. "This page is 4 revisions behind xxx.git, and 1 revision ahead" (indicating that some updates are missing, but that there are local changes), and allowing PR's from the forked wiki to its parent. But that could be secondary to the simple change proposed in 1. What are the chances?
... View more