-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
[Wiki additions] #77
Comments
Oh, thanks!!!!!!!!!! Why can it not do PRs? That seems bad since I can't keep track of all forks and whether they changed their wikis...... I bet there is a way..... |
I've pushed it 😄 |
Because Github (and Gitlab) both consider Wikis as small stuff that only the lead devs should touch it seems. Even though they both implement Wikis as regular repositories. This is quite ridiculous as everyone in the communities are asking for the ability to use wikis as normal repositories...
Yeah I do not quite like this workaround either, but there is not better way for Github/Gitlab wikis. People that are eventually fed-up with that often move to static site generator (hugo or readthedocs for instance), create a separate repo for their doc and have a pipeline to automatically build and publish the latest push. But this is quite cumbersome. Anyway, I am going to complete the wiki today so I is up to date with the current status of the README and doc/ |
Thx for the wiki work! Well, for the time being, I can pull your stuff when you notify me. Isn't there a way to just fork the wiki repository? When you change from the wiki tab to the code tab? |
Nope, no way to fork. What I had to do is:
|
Adding stuff to the wiki according to this method (see #75 (reply in thread)).
As the method says,
To merge, you need to
cd
into itgit pull [email protected]:lambtho12/telekasten.nvim.wiki.git
This issue only serves to notify you that new changes have been added to (my fork of) the wiki and need to be pulled.
The text was updated successfully, but these errors were encountered: