[Feature/giscus] add giscus support

[sgamerw]

Description

add giscus support, not add config to site.config.ts, maybe too simple and crude, but it works.

Notion Test Page ID

I test it locally, and comment success to giscus repo.
https://github.com/orgs/giscus/discussions/1160

[vercel]

@sgamerw is attempting to deploy a commit to the Saasify Team on Vercel.

A member of the Team first needs to authorize it.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@giscus/react@2.3.0	None	0	30 kB	laymonage
npm/@lit-labs/ssr-dom-shim@1.1.1	environment	0	33.7 kB	lit-robot
npm/@lit/reactive-element@1.6.3	None	0	788 kB	lit-robot
npm/@types/trusted-types@2.0.3	None	0	8.97 kB	types
npm/giscus@1.3.0	None	0	12.1 kB	laymonage
npm/lit-element@3.3.3	None	0	150 kB	lit-robot
npm/lit-html@2.8.0	None	0	1.81 MB	lit-robot
npm/lit@2.8.0	None	0	109 kB	lit-robot
npm/notion-client@6.16.0	Transitive: filesystem, network	+5	455 kB	fisch0920
npm/notion-types@6.16.0	None	0	77.4 kB	fisch0920
npm/notion-utils@6.16.0	None	0	118 kB	fisch0920
npm/react-notion-x@6.16.0	eval	0	2.04 MB	fisch0920

🚮 Removed packages: npm/notion-client@6.15.6, npm/notion-types@6.15.6, npm/notion-utils@6.15.6, npm/react-notion-x@6.15.6

View full report↗︎

[laymonage]

Thank you for this PR, but please don't use these as the default, otherwise people who haven't configured the values with their own repo will spam the giscus repo with their discussions.

[sgamerw]

so, maybe just keep these configuration empty, then tell users how to set these in docs/wiki/readme?

[sgamerw]

I haven't add configs to site.config.ts, there are too many values, so what's your suggestion?

[sgamerw]

@laymonage already remove the giscus repo information, made these keys into config for giscus.

[transitive-bullshit]

This looks like a really great starting point for Giscus support, which I'm a fan of. I don't think it should be enabled by default or, as you mentioned, it should be optional and configured via the config file.

[sgamerw]

Thanks for reply, I'll add config for Giscus ASAP.

[YesYouKenSpace]

Is this not ready? @sgamerw @transitive-bullshit

[yanyanlongxia]

Glad to see this feature still works!
I've successfully deployed giscus in my site. Thank you guys!

[sgamerw]

This looks like a really great starting point for Giscus support, which I'm a fan of. I don't think it should be enabled by default or, as you mentioned, it should be optional and configured via the config file.

@transitive-bullshit hi, already add configs and Giscus was disabled by default.

[sgamerw]

I'm really looking forward to this feature. I hope this can be implemented soon!

already done，wait for reviewer to approve.