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

Automatically create threads for specified channels #134

Closed
vcarl opened this issue Dec 18, 2021 · 3 comments · Fixed by #147
Closed

Automatically create threads for specified channels #134

vcarl opened this issue Dec 18, 2021 · 3 comments · Fixed by #147
Assignees

Comments

@vcarl
Copy link
Member

vcarl commented Dec 18, 2021

For specified channels:

  • every message has a thread created for it, named something readable (name + date stamp?)
  • replies are removed and the sender Dm'd instructions
  • a !close command only the author can use (or maybe mvps and maybe a "helper" type role with this ability as well)
    • this is maybe not helpful, cuz afaik members can always close their own threads
  • reactibot closes after 6 hours, and sends a message with instructions on following up
  • instructions link to parent message and suggest replying to it if it's relevant
@Padmanabh82
Copy link

I have more suggestions like, bot will pin the threads that are active or not being answered and thread's name should include timestamp, name of author, whole error or question (like why this unexpected behaviour is occurring)

@vcarl
Copy link
Member Author

vcarl commented Jan 2, 2022

Instead of a !close command, I think instead a ✅ reaction that will mark an answer as "accepted" and close the thread immediately is more helpful

@nickserv
Copy link
Member

nickserv commented Jan 2, 2022

I believe we can also use buttons for this since we've upgraded the API, though I'm not sure if they require supporting commands.

@vcarl vcarl linked a pull request Jan 2, 2022 that will close this issue
@vcarl vcarl closed this as completed in #147 Jan 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants