utterances
utterances copied to clipboard
Selectively Choose to Post to GitHub Discussions or Issues
Can an option to be added where the site owner and/or the end-user can choose if the comment goes to GitHub Issues or GitHub Discussions (for repositories with it enabled).
In the case of GitHub Discussions, additional stylings may be needed.
The author can choose whether it goes to GitHub Discussions if it is a comment and if it goes to GitHub Issues if it is an issue with the page or content. Each item can say if it is an Issue or Discussion item. They can be displayed intermingles or one group before the other (e.g. Discussions before Issues).
Discussions has been available now for all public repositories, can't wait for utterances' support.
https://github.blog/2020-12-08-new-from-universe-2020-dark-mode-github-sponsors-for-companies-and-more/
It seems like the discussions API has been opened up for all users!
https://github.com/github/feedback/discussions/43#discussioncomment-399047 https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions
This would be great if discussions could be used, then the issues could be kept clear for regular issues.
Additionally, if Utterances can be adapted to the Q&A part of discussions, then it can be used more for discussion and forum posts. I don't know how difficult this would be, and it might not be a viable option, but if it is I would really like to see it!
Has anyone found the time to make strides on this? I'm very interested in this feature. I love the idea of using issues, but it conveys the idea that they are issues. Instead, a Github discussion entry seems more viable -- considering the API is publicly exposed.
@sirinath @batkiz @brainkim @cole-wilson @t-h-o and others who might be interested,
I've built exactly this: giscus!
GitHub's Discussions API is very different from the Issues API, so I decided to create an entirely new project. Let me know how you like it!
Thanks, this is great! I'm actually planning to use both Giscus and Utterances.