Skip to content
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

Enhancement (Core Feature): Add thread and forum to GitHub discussion #1

Open
JacobCoffee opened this issue Sep 18, 2023 · 3 comments
Labels
byte 🤖 Related to the Byte bot service enhancement ➕ This is a brand new feature or request

Comments

@JacobCoffee
Copy link
Owner

JacobCoffee commented Sep 18, 2023

Summary

The entire idea behind Byte was that there exists no other solution whereby we can take a threaded discussion or forum post on a Discord guild and push it somewhere like GitHub discussions.

There is some bot that makes them indexable, but it uploads it to their own website, and it isn't the perfect solution.

Asks:

  • Have it usable as a command inside of the current thread or forum post. @byte, upload this to GitHub
  • Have it (configurable) automatically attach to any new/current/non-solved thread or forum post and automatically upload it daily/when marked solved/etc.
  • Have a command to detach from a thread or forum post even if it is not marked with the (configurable) Exclude from GitHub tag

Basic Example

  • Have Byte read the thread or forum post
  • Send to GitHub GraphQL API: https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions#creatediscussion
  • Periodically check discussions, mark them as closed when the chosen tag is set. Ideally this is something like Solved or Completed but should be configurable by the guild owner.
  • Additionally, there should be a user-definable tag that allows discussions to not be uploaded at all (maybe it is not relevant, or too abstract.) Something like Exclude from GitHub.

Here, the solved posts should update the relevant GitHub discussion and mark it as closed, and it should make sure to not upload any discussions from the Code Review post.
image

Drawbacks and Impact

Threads do not have tags, so it makes things hard and may be out of scope. Forum posts would be enough for this, and should allow us a lot more flexibility (❓)

Unresolved questions

  • How do we respect Discord tags? (Exclude from GitHub, Solved, etc.)

Note

We utilize Polar.sh to engage in regular as well as pledge-based > sponsorship.

Check out all issues funded or available for funding on our Polar.sh dashboard

  • If you would like to see an issue prioritized, make a pledge towards it!
  • We receive the pledge once the issue is completed & verified
  • This, along with engagement in the community, helps us know which features are a priority to our users.
Fund with Polar
@JacobCoffee JacobCoffee added the enhancement ➕ This is a brand new feature or request label Sep 18, 2023
@JacobCoffee JacobCoffee added the byte 🤖 Related to the Byte bot service label Nov 6, 2023
@JacobCoffee
Copy link
Owner Author

https://github.com/AnswerOverflow/AnswerOverflow does this.

To stay within TOS we need to remind users that their content will be sent elsewhere.

@JacobCoffee
Copy link
Owner Author

Mark specific message as answer: (to be sent to GH)
I'm thinking send question thread to GH as a Q&A, reply the this a 2nd time with the message marked as the answer, and then mark that as the answer to the GH Q&A discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
byte 🤖 Related to the Byte bot service enhancement ➕ This is a brand new feature or request
Projects
None yet
Development

No branches or pull requests

1 participant