Restrict Giscus Origins about jekyll-theme-chirpy HOT 5 CLOSED

The situation is a bit awkward, this feature requires a file giscus.json to be created in the repo root directory.

Currently I have no way to decide whether to generate this file based on the site config. If a user doesn't use giscus, then his/her repository will have a useless giscus.json.

Perhaps you can create this file in your own repo and configure it as needed.

from jekyll-theme-chirpy.

I see. Couldn't you just generate the file if the key giscus.repo is defined in _config.yml? Otherwise I agree, I can just create a giscuss.json

from jekyll-theme-chirpy.

Ah, nevermind. This would always be undefined when the site is generated.

from jekyll-theme-chirpy.

I see. Couldn't you just generate the file if the key giscus.repo is defined in _config.yml? Otherwise I agree, I can just create a giscuss.json

To the best of my knowledge, this is not achievable, as expressed in my comment above.

from jekyll-theme-chirpy.

I will close it then, I totally understand why this would be confusing for some and there is a workaround if using giscus.

from jekyll-theme-chirpy.