![]() Update, : After several months of trying giscus, I decided to remove it, as explained in “ Letting go of giscus.” Netlify Edge Functions So that’s one more thing you have to do in such a case. Later update: Turned out that, while the previous comments and reactions were indeed back on the site, it wasn’t possible for anyone to enter new ones - until (and, again, I have Sarah Rainsberger to thank for giving me the word that things were amiss) I went back into the giscus website and obtained a new set of variables for the comments repo. (Thanks to the Astro team’s Sarah Rainsberger for the idea!) So, now, the comments live in a comments repo, where they should be eternally safe from my fickleness. However, I’d missed the most sensible solution of all: give the GitHub Discussions their own separate repo and point giscus to it from, well, whichever repo may be hosting this site at whatever time. However, as of now, that’s not possible unless you change each Discussion’s category away from the giscus-recommended category of “Announcements.” Then you can transfer each Discussion to the new repo, and change it back to an “Announcements” Discussion - and all your comments magically come back in the new place. If you change the site to a different repo, the Discussions must be transferred to that repo otherwise, they won’t appear in the new repo’s giscus-equipped website. for commenting on your website, its reliance on GitHub Discussions means that comments are tied to the repo where your website’s code exists. I then posted word of this to a few Discords where I thought it might be useful and, for the same reason, I will reproduce some of that post here: Within a few minutes, I was able to get those Discussions transferred across and, with them, their comments restored to the appropriate pages in the site. ![]() ![]() Every time I attempted it, GitHub gave me an error message saying that what I was attempting wasn’t possible “at this time.”įinally, yesterday, giscus maintainer Sage Abdullah figured it out. I tried for days and couldn’t get it to work. The problem came in the transfer process. Yes, if you transfer the Discussions to the new repo, the website will still have the same comments as when it was on the old repo (presuming, of course, that you have properly configured the new repo to use giscus). Still, even after I did, I figured, Ah, no problem, I’ll just transfer the Discussions from the previous repo to the new one, and everything will work again. giscus uses the GitHub Discussions API and brings in comments from Discussions that it automatically creates on your site’s repository.Īt the time I issued that post, I had no expectation of migrating the site to a different repo. I noted in the previous “ Gems in the rough” that I was trying the giscus commenting system. As a result, certain content on this page could be at variance with what you’re currently seeing on the site, but the two were consistent when this post originally appeared.Įach entry in the “Gems in the rough” series is a collection of tips, explanations, and/or idle observations which I hope will be at least somewhat useful to those of you with websites built by static site generators (SSGs). General note: This site’s appearance, configuration, hosting, and other basic considerations will change over time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |