Skip to content

improving giscus repo comment in _config.yml #2477

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

Closed
wants to merge 1 commit into from

Conversation

minxsecurity
Copy link

Type of change

  • Documentation update

Description

updated comment next to giscus repo parameter to help others know that it should be the same repo as the github pages repo. otherwise you will get content security policy errors and it won't load properly.

I mistakenly was under the impression that you had to fork/clone the giscus repo into your personal repository, and use that instead, and wanted to hopefully help out someone else in case they had the same thought.

Additional context

updated comment next to giscus repo parameter to improve clarity that it should be the same repo as the github pages repo. otherwise you will get CSP errors and it won't load properly.

Signed-off-by: Dolly Minx <github@dollyminx.com>
@cotes2020
Copy link
Owner

Thank you for your PR! However, I don't think the original comment needs to be changed. In fact, you can create a separate repository for storing Giscus comments for your site. If you have more questions, please refer to the documentation on https://giscus.app/.

@cotes2020 cotes2020 closed this Jul 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants