You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey folks, first of all thanks for the project and all the work accomplished, it truly looks amazing.
I'm facing an issue when using giscus on a private repository. When I try to add a comment, even though the discussion is being created the comments are not being added nor loaded (in case the discussion already have comments). When I open up the network tab I can find an error on the request that is supposed to get the comments:
{"error":"Discussion not found"}
Any idea on what it could be? This is how I'm loading the script:
P.S.: I've already double checked and the script is loading the site object variables correctly. It used to work before with that same configuration but it suddenly stopped working sometime around last month.
The text was updated successfully, but these errors were encountered:
Hey folks, first of all thanks for the project and all the work accomplished, it truly looks amazing.
I'm facing an issue when using giscus on a private repository. When I try to add a comment, even though the discussion is being created the comments are not being added nor loaded (in case the discussion already have comments). When I open up the network tab I can find an error on the request that is supposed to get the comments:
{"error":"Discussion not found"}
Any idea on what it could be? This is how I'm loading the script:
<script src="https://giscus.app/client.js" data-repo="{{ site.giscus.data_repo }}" data-repo-id="{{ site.giscus.data_repo_id }}" data-category="General" data-category-id="{{ site.giscus.data_category_id }}" data-mapping="pathname" data-strict="0" data-reactions-enabled="1" data-emit-metadata="0" data-input-position="bottom" data-theme="dark" crossorigin="anonymous" async></script>
P.S.: I've already double checked and the script is loading the site object variables correctly. It used to work before with that same configuration but it suddenly stopped working sometime around last month.
The text was updated successfully, but these errors were encountered: