Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Giscus fails when repository contains capitals
See original GitHub issueDiscovered this when using Giscus with Jekyll as part of https://github.com/mmistakes/minimal-mistakes/pull/3022
The PR takes the repository name from a setting, which in my case was SeanKilleen/seankilleen.github.io.
Giscus failed with a 400 error when retrieving comments, so thought there was no discussion topic, and therefore kept creating new discussion topics.
I think the issue is that the GitHub API or similar might be failing with a repo name that contains uppercase characters. I’ll see if I can submit a PR to make that behavior case insensitive.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@laymonage confirmed – #124 resolved this issue. 👍 Thanks!
@LazyRen It turns out that the issue is unrelated, I’ve shipped https://github.com/laymonage/giscus/commit/bca513c72a5a3b309cce4a864b042a2e82c66c48 which should fix it.
@SeanKilleen I cannot reproduce the error, the following works fine:
Could you copy the
<iframe>'s src when it happens and paste it here?