-
-
Notifications
You must be signed in to change notification settings - Fork 355
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
feat: add giscus comments system #448
Conversation
✅ Deploy Preview for anatole-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xjasonlyu LGTM. Thanks for your PR.
@xjasonlyu Would you mind adding a sample configuration as a coment that I could add to the wiki? Thanks. |
Yes, sure thing! Adding GiscusFirst generate the config according to the official document, and then enter those params in the [params.giscus]
repo = "githubuser/reponame"
repoID = "Github Repo ID"
category = "Discussions Category"
categoryID = "Discussions Category ID"
# <Optional Params>
# mapping = "pathname"
# strict = "0"
# reactionsEnabled = "1"
# emitMetadata = "0"
# inputPosition = "bottom"
# lang = "en"
# loading = "lazy" |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Description
Adding the support for Giscus Comments System, a comments system powered by GitHub Discussions.
Giscus was heavily inspired by utterances, but with more config options and a better UI.
Issue Number:
Feature Request for #446
Additional Information (Optional)
Example/configuration can be found and generated at giscus.
Demo with Giscus
Light mode:
Dark mode:
Checklist
Yes, I included all necessary artefacts, including:
Testing Checklist
Yes, I ensured that all of the following scenarios were tested:
Notify the following users