Skip to content

recipient_thread_close via Buttons #3363

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

Conversation

martinbndr
Copy link
Contributor

  • Updates the recipient_thread_close feature to use a button instead of a reaction.
  • New config options: recipient_thread_close_button_label, recipient_thread_close_button_style
  • The close_emoji default value is now None to make it possible changing the button to only have a label.

Taaku18 and others added 11 commits January 16, 2025 00:22
Signed-off-by: Taku <[email protected]>
Implements a checking mechanismen for local git repository.
This fixes some incorrect help text of the thread_close_response and thread_self_close_response
- Updates the recipient_thread_close feature to use a button instead of a reaction.
- New config options: recipient_thread_close_button_label, recipient_thread_close_button_style
- The close_emoji default value is now None to make it possible changing the button to only have a label.
@martinbndr
Copy link
Contributor Author

Oh no I think I messed up with the commits to actually only include the required one for the update

@martinbndr
Copy link
Contributor Author

3ebb21e and e3af5fa are for the recipient_thread_close update

@martinbndr
Copy link
Contributor Author

Will recreate it to have only correct commits in it.

@martinbndr martinbndr closed this Feb 28, 2025
@martinbndr martinbndr deleted the update_recipient_thread_close branch February 28, 2025 10:42
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 this pull request may close these issues.

2 participants