Re:Tell HN: GitHub Organizations not as free as it seems
by TimTheTinker on Thursday April 23, 2020 @04:15PM
(#22960696)
Seriously, you should store wiki pages as .md files in a /wiki folder in your repo, regardless of your git repo hosting provider. I'm positive wiki pages are stored in a separate git repo alongside your code, anyway.
The more that lives in the codebase itself, the better -- ideally this would not only include wiki pages, but also issues, comments, PR threads, etc.
Re:Tell HN: GitHub Organizations not as free as it seems
by tedivm on Thursday April 23, 2020 @04:18PM
(#22960743)
Github treats wikis as another git repository. I regularly use this to backup the wikis I have on github.
If your project is named `username/repository` then your wiki can be cloned at `git clone [email protected]:username/repository.wiki.git`.
Re:Tell HN: GitHub Organizations not as free as it seems
by ribadeodev on Friday April 24, 2020 @01:52AM
(#22965065)
This approach is something I never quite figured out. What is the point of documenting your project in another repository? Based on what OP just explained this is one of the only explanations I can come up with (GitHub treats this as an extra that you must pay for).
Seriously for organizations, you're better of in self-hosting your own projects on-premise with open-source alternatives like GitLab (recommended), cgit or even Gerrit to avoid nonsense like 'centralising everything to GitHub' in the long term. [0]
[0] https://news.ycombinator.com/item?id=22868406