11–20 of 20 posts
It reminds me migrating own GitHub repo Travis CI from https://travis-ci.org to https://travis-ci.com, which is also one-way process.
Some of my repo older still use travis-ci.org (ORG domain is cool here), but all new GitHub repos could be linked only to travis-ci.com (COM domain little terrible)
Yup, nobody in all the announcements or any other articles mentioning this new "github" has mentioned the WIKI (which is part of Gitlab) is not included in the free part of Github ... this is kind of critical IMHO
Have you contacted their customer support? I wonder if the data is still there, or can be recovered out somehow.
The fact that this is even necessary just screams monumental f up.
Here is a free upgrade. (With surprise data loss)
Yup, nobody in all the announcements or any other articles mentioning this new "github" has mentioned the WIKI (which is part of Gitlab) is not included in the free part of Github ... this is kind of critical IMHO
Really, the wiki is one of the worst features. Markdown based docs are far better and actually part of the repository
But it is documented and from the very beginning. If you look at this page https://github.com/pricing in the comparison table under Pages and Wiki it clearly says "Public repositories". I'm guessing you had a private one. I've also moved from Pro to Free Teams and I've seen this from the start.
if you mean "clearly" by it shows a checkmark beside "wikis" and if you click a chevron to expand the paragraph and find it says "for public repos" then sure.
Yup, nobody in all the announcements or any other articles mentioning this new "github" has mentioned the WIKI (which is part of Gitlab) is not included in the free part of Github ... this is kind of critical IMHO
Really, the wiki is one of the worst features. Markdown based docs are far better and actually part of the repository
Have you contacted their customer support? I wonder if the data is still there, or can be recovered out somehow.
Earlier quoted context omitted.
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.
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 git@github.com:username/repository.wiki.git`.
