| Commit message (Collapse) | Author | Age | Lines | 
| ...    |  | 
| | | | 
| | | 
| | | 
| | |  | 
This will help clarify the relationship between the button & the viw since it'll only be used there
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | | 
| | | 
| | | 
| | |  | 
This also renames to method to align more with our fetch or {action} pattern
 | 
| | | |\  
| |_|/  
|/| |    | 
 | 
| |\ \ \  
| | | | 
| | | |  | 
include Thread & PrivateChannel in get_or_fetch_channel return types
 | 
| | |\ \ \  
| |/ / /  
|/| | |    | 
 | 
| | |/ /  
|/| |   
| | |   
| | |   
| | |    | 
Made the tag more brief without any substantial changes to its overall approach.
Co-authored-by: wookie184 <[email protected]>
 | 
| |/ /   | 
 | 
| |\ \  
| | | 
| | |  | 
Don't close already closed posts
 | 
| |/ /   | 
 | 
| |\ \  
| | | 
| | |  | 
Link directly to the sqlite3 placeholder howto
 | 
| | |\ \  
| |/ /  
|/| |    | 
 | 
| |\ \ \  
| | | | 
| | | |  | 
Help forum improvements
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | | 
| | | | 
| | | | 
| | | |  | 
thread_create events are triggered before the thread's starter message is available, so listening for starter messages with on_message instead ensures we have a message object to use.
 | 
| | | | | 
| | | | 
| | | | 
| | | | 
| | | | 
| | | |  | 
I decided to keep the archive logic simple, and just go for 30 minutes since last message, rather than the hybrid of 30 mins + 10 depending on who sent the last message.
The reason for using the hybrid approach previously was due to us running out of channels frequently
Since this is no longer a problem, I decided to keep the logic simple.
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| |/ / /   | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | | 
| | | 
| | | 
| | |  | 
This documents the attributes the class has, which gives better context for future readers/contributors
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | | 
| | | 
| | | 
| | |  | 
This also enhances the docstrings for a better clarification of its purpose
 | 
| | | |  | 
 | 
| | | | 
| | | 
| | | 
| | |  | 
prepare_self_assignable_roles_view
 | 
| | | |  | 
 | 
| | | | 
| | | 
| | | 
| | | 
| | |  | 
The messages were intended for a button that will automatically assign all availables roles to the interactor
This changes since it's not the intended behavior
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | | 
| | | 
| | | 
| | |  | 
appropriate roles
 | 
| | | |  | 
 | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | |  | 
This comes with another dependency to try to locate the message that needs to hold the view.
If that message is not found, a new one will be created & sent.
 | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | |  | 
ClaimAllSelfAssignableRolesButton button
Note that these are still dummy views & have no behavior
 | 
| | |/  
|/|    | 
 | 
| |\ \  
| | | 
| | |  | 
Bump bot core version
 | 
| | | | 
| | | 
| | | 
| | |  | 
These errors can be caused by the message being deleted, or the message being in an archived thread
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| |/ /   | 
 | 
| |\ \  
| | | 
| | |  | 
Misc Fixes For Help Forum
 | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | |  | 
Co-authored-by: Boris Muratov <[email protected]>
Co-authored-by: Amrou Bellalouna <[email protected]>
Signed-off-by: Hassan Abouelela <[email protected]>
 | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | |  | 
In the case of an image or other media as the starter message, the
formatted message in the help DM will be empty, which is invalid for the
embed. We populate the field with some more useful text in this case.
Signed-off-by: Hassan Abouelela <[email protected]>
 | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | |  | 
Similar to 555ed4e9, the pagination utility needs to catch when it's
trying to act on an archived thread.
Signed-off-by: Hassan Abouelela <[email protected]>
 | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | |  | 
The wait_for_deletion utility would try to remove reactions from a
message after the timeout expires, which would normally be fine. In
threads however, they can be closed while waiting for the timeout to
expire. In such a case, the bot will try to remove the reactions after
the channel has been closed and fail. A special exception was added for
this case to do nothing, since this is only a QoL feature.
Signed-off-by: Hassan Abouelela <[email protected]>
 |