aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Merge pull request #1054 from python-discord/dm_relayGravatar Leon Sandøy2020-07-15-6/+43
|\ | | | | DM relay - minor fixes
| * Merge branch 'master' into dm_relayGravatar Leon Sandøy2020-07-15-70/+202
| |\ | |/ |/|
* | Merge pull request #1041 from python-discord/dm_relayGravatar Kieran Siek2020-07-15-107/+198
|\ \ | | | | | | Relay all DMs sent to the bot to #dm_log
| * \ Merge branch 'master' into dm_relayGravatar Kieran Siek2020-07-15-15/+49
| |\ \ | |/ / |/| |
* | | Merge pull request #1044 from python-discord/talentpool-oldestGravatar Kieran Siek2020-07-15-5/+43
|\ \ \ | | | | | | | | Allow ordering talentpool/bigbrother watched users by oldest added
| * \ \ Merge branch 'master' into talentpool-oldestGravatar kosayoda2020-07-15-10/+6
| |\ \ \ | |/ / / |/| | |
* | | | Merge pull request #1051 from ↵Gravatar Dennis Pham2020-07-14-7/+6
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | python-discord/bug/info/1050/remove-help-reactions-404 Suppress NotFound when removing help command reactions
| * \ \ \ Merge branch 'master' into bug/info/1050/remove-help-reactions-404Gravatar Dennis Pham2020-07-14-3/+0
| |\ \ \ \ | |/ / / / |/| | | |
* | | | | HelpChannels: remove cooldown info from available messageGravatar MarkKoz2020-07-14-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Users can no longer see available channels if they're on cooldown. They will instead see a special "cooldown" channel which will explain what's going on.
| * | | | Suppress NotFound when removing help cmd reactionsGravatar MarkKoz2020-07-14-7/+6
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | The message may be deleted somehow before the wait_for times out. Fixes #1050 Fixes BOT-6X
| * | | Document new kwarg in docstringGravatar kosayoda2020-07-15-0/+2
| | | |
| * | | Merge branch 'master' into talentpool-oldestGravatar Dennis Pham2020-07-14-55/+143
| |\ \ \ | |/ / / |/| | |
| * | | Achieve feature parity with talentpoolGravatar kosayoda2020-07-14-2/+17
| | | |
| * | | Add command to list nominees by oldest firstGravatar kosayoda2020-07-14-0/+11
| | | |
| * | | Accept argument to order nominees by oldest firstGravatar kosayoda2020-07-14-2/+6
| | | |
| * | | Pass argument as kwarg to preserve functionalityGravatar kosayoda2020-07-14-1/+1
| | | |
| * | | Allow ordering watched users by oldest firstGravatar kosayoda2020-07-14-1/+7
| | | |
| | * | Merge branch 'master' into dm_relayGravatar Leon Sandøy2020-07-15-55/+153
| | |\ \ | |_|/ / |/| | |
* | | | Merge pull request #1032 from slushiegoose/sanitize-bot-outputGravatar Mark2020-07-14-53/+141
|\ \ \ \ | | | | | | | | | | Sanitize bot output
| * | | | fix misaligned indentationGravatar Slushie2020-07-14-37/+37
| | | | |
| * | | | edit snekbox tests to work with filteringGravatar Slushie2020-07-13-0/+12
| | | | |
| * | | | check for the filter_cog in case it is unloadedGravatar Slushie2020-07-13-1/+3
| | | | |
| * | | | rename the `_filter_eval` function to be a public functionGravatar Slushie2020-07-13-2/+2
| | | | |
| * | | | Add missing variable assignment to stop NameErrors occurringGravatar Slushie2020-07-09-0/+1
| | | | |
| * | | | Fix missing hypenGravatar slushiegoose2020-07-09-1/+1
| | | | | | | | | | | | | | | Co-authored-by: Leon Sandøy <[email protected]>
| * | | | Call the filter eval command after receiving an eval resultGravatar Slushie2020-07-08-1/+6
| | | | |
| * | | | Create a filtering function to filter eval resultsGravatar Slushie2020-07-08-52/+120
| | | | |
| * | | | Edit BadArgument error messageGravatar Slushie2020-07-08-1/+1
| | | | |
* | | | | Remove redundant kwarg in !kick and !shadow_kickGravatar kosayoda2020-07-14-2/+2
| |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | The kwarg `active=False` is already being passed in `apply_kick`, therefore passing it in the parent callers result in a TypeError. Fixes #976 Fixes BOT-5P
* | | | Whitelisting some popular communitiesGravatar Leon Sandøy2020-07-13-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following communities are whitelisted by this commit: - Django - Programming Discussions - JetBrains Community - Raspberry Pi - Programmers Hangout - SpeakJS - DevCord - Unity - Programmer Humor - Microsoft Community Most of these are partners, or otherwise friendly communities that aren't worth pinging mods over.
| | | * Oops, these prints shouldn't be here.Gravatar Leon Sandøy2020-07-15-3/+0
| | | | | | | | | | | | | | | | https://github.com/python-discord/bot/issues/1041
| | | * How did that except except block get in?Gravatar Leon Sandøy2020-07-15-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | Weird. https://github.com/python-discord/bot/issues/1041
| | | * Create a UserMentionOrID converter.Gravatar Leon Sandøy2020-07-15-1/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we're using the !reply command, using a regular UserConverter is somewhat problematic. For example, if I wanted to send the message "lemon loves you", then I'd try to write `!reply lemon loves you` - however, the optional User converter would then try to convert `lemon` into a User, which it would successfully do since there's like 60 lemons on our server. As a result, the message "loves you" would be sent to a user called lemon.. god knows which one. To solve this bit of ambiguity, I introduce a new converter which only converts user mentions or user IDs into User, not strings that may be intended as part of the message you are sending. https://github.com/python-discord/bot/issues/1041
| | | * Ves' refactorGravatar Leon Sandøy2020-07-15-15/+16
| | | | | | | | | | | | Co-authored-by: Sebastiaan Zeeff <[email protected]>
| | | * Add some stats for DMs sent and received.Gravatar Leon Sandøy2020-07-15-0/+3
| | | | | | | | | | | | | | | | https://github.com/python-discord/bot/issues/1041
| | | * Add the user ID to the username in dm relays.Gravatar Leon Sandøy2020-07-15-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Without this, it is difficult to know precisely who the user that is DMing us is, which might be useful to us. https://github.com/python-discord/bot/issues/1041
| | | * Restore DM user caching.Gravatar Leon Sandøy2020-07-15-6/+22
| | |/ | | | | | | | | | This reverts commit 042f472a
| | * Remove caching of last_dm_user.Gravatar Leon Sandøy2020-07-15-25/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you're typing up a reply and the bot gets another DM while you're typing, you might accidentally send your reply to the wrong person. This could happen even if you're very attentive, because it might be a matter of milliseconds. The complexity to prevent this isn't worth the convenience of the feature, and it's nice to get rid of the caching as well, so I've decided to just make .reply require a user for every reply. https://github.com/python-discord/bot/issues/1041
| | * Merge branch 'master' into dm_relayGravatar Leon Sandøy2020-07-13-173/+169
| | |\ | |_|/ |/| |
* | | Merge pull request #1039 from ↵Gravatar Dennis Pham2020-07-13-4/+16
|\ \ \ | | | | | | | | | | | | | | | | python-discord/1038_allow_role_mentions_in_specific_areas Allow role mentions in specific areas
| * \ \ Merge branch 'master' into 1038_allow_role_mentions_in_specific_areasGravatar Dennis Pham2020-07-13-169/+153
| |\ \ \ | |/ / / |/| | |
* | | | Fix rescheduling of edited infractionsGravatar MarkKoz2020-07-12-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | It was attempting to schedule a dictionary instead of a coroutine. Fixes #1043 Fixes BOT-6Y
* | | | Merge pull request #1017 from python-discord/feat/backend/800/scheduler-redesignGravatar Mark2020-07-12-169/+153
|\ \ \ \ | | | | | | | | | | Scheduler Redesign
| * \ \ \ Merge branch 'master' into feat/backend/800/scheduler-redesignGravatar Mark2020-07-12-217/+683
| |\ \ \ \ | |/ / / / |/| | | |
| * | | | Scheduler: document coroutine closing elsewhereGravatar MarkKoz2020-07-06-4/+12
| | | | |
| * | | | Scheduler: assert the coroutine hasn't been awaited yetGravatar MarkKoz2020-07-06-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It'd fail to schedule the coroutine otherwise anyway. There is also the potential to close the coroutine, which may be unexpected to see for a coroutine that was already running (despite being documented).
| * | | | Scheduler: more verbose logging in _await_laterGravatar MarkKoz2020-06-30-7/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Showing the task ID in the logs makes them distinguishable from logs for other tasks. The coroutine state is logged because it may come in handy while debugging; the coroutine inspection check hasn't been proven yet in production.
| * | | | Scheduler: explain the name param in the docstringGravatar MarkKoz2020-06-29-0/+4
| | | | |
| * | | | Scheduler: add details to class docstringGravatar MarkKoz2020-06-29-1/+11
| | | | |
| * | | | Scheduler: only close unawaited coroutinesGravatar MarkKoz2020-06-25-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The coroutine may cancel the scheduled task, which would also trigger the finally block. The coroutine isn't necessarily finished when it cancels the task, so it shouldn't be closed in this case.
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-26 10:44:58 +0000