aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* consider parent channels when checking mod channelsGravatar Chris Lovering2021-10-31-2/+7
|
* Merge pull request #1923 from Lainika/GH-1873_Fix_embedsGravatar Karlis Suvi2021-10-31-2/+1
|\
| * GH-1873 Fix BigBrother embedsGravatar Lainika2021-10-31-2/+1
|/ | | | Move text from footer to description.
* Merge pull request #1793 from python-discord/cleanreworkGravatar Johannes Christ2021-10-30-274/+614
|\ | | | | Clean Cog Rework
| * Merge branch 'main' into cleanreworkGravatar wookie1842021-10-30-10/+64
| |\ | |/ |/|
* | Merge pull request #1909 from python-discord/pin-consistencyGravatar Johannes Christ2021-10-28-3/+9
|\ \ | | | | | | Unpin All Messages When Moving Help Channels
| * \ Merge branch 'main' into pin-consistencyGravatar Johannes Christ2021-10-28-7/+55
| |\ \ | |/ / |/| |
* | | Handle autoban filtering in DMs (#1914)Gravatar Boris Muratov2021-10-26-1/+2
| | | | | | | | | An autoban trigger being sent in DMs caused the ban to fail, but for it to still be registered in the database. That is becuase the ban command uses the `ctx.guild.ban` method, but in DMs `ctx.guild` is None. This commit solves it by overriding the `context.guild` field.
* | | Merge pull request #1893 from python-discord/filters/autobanGravatar Boris Muratov2021-10-25-7/+54
|\ \ \ | | | | | | | | Filtering: add autoban on specific reasons
| * | | Filtering: remove dangling empty quoteGravatar Matteo Bertucci2021-10-25-1/+1
| | | | | | | | | | | | Co-authored-by: ChrisJL <[email protected]>
| * | | Filtering: update auto-ban commentsGravatar Matteo Bertucci2021-10-25-3/+4
| | | | | | | | | | | | Co-authored-by: ChrisJL <[email protected]>
| * | | Filtering: fix ban flowGravatar Matteo Bertucci2021-10-25-2/+3
| | | |
| * | | Fltering: clean up autoban codeGravatar Matteo Bertucci2021-10-25-4/+4
| | | |
| * | | Filter list: move warning to #mod-metaGravatar Matteo Bertucci2021-10-25-4/+4
| | | |
| * | | Merge remote-tracking branch 'origin/main' into filters/autobanGravatar Matteo Bertucci2021-10-25-303/+360
| |\ \ \ | |/ / / |/| | |
| * | | Filter list: send warning when autoban trigger is addedGravatar Matteo Bertucci2021-10-25-2/+11
| | | |
| * | | Filtering: update auto ban messageGravatar Matteo Bertucci2021-10-25-3/+15
| | | |
| * | | Infrac: prioritize mod over bot feedback msgGravatar Matteo Bertucci2021-10-25-8/+8
| | | |
| * | | Filtering: make autoban tempGravatar Matteo Bertucci2021-10-19-8/+4
| | | |
| * | | Filtering: do not try to convert to a memberGravatar Matteo Bertucci2021-10-19-2/+2
| | | |
| * | | Filtering: update auto-ban messageGravatar Matteo Bertucci2021-10-19-2/+2
| | | | | | | | | | | | Co-authored-by: Boris Muratov <[email protected]>
| * | | Filtering: add autoban on specific reasonsGravatar Matteo Bertucci2021-10-19-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to the increase in typo-squatting based phishing, we want to automatically ban users sending specific domain names. For that, this commit will automatically ban any user that trigger a filter which has `[autoban]` in its reason. That's it!
| | * | Unpin All Messages When Moving Help ChannelsGravatar Hassan Abouelela2021-10-24-3/+9
| |/ / |/| | | | | | | | | | | | | | | | | | | | Occasional hiccups in the Discord API would cause unpinning in help channel to sometimes fails. This gets around that by unpinning all messages when making the channel available. Signed-off-by: Hassan Abouelela <[email protected]>
| | * Remove channel limitation with time rangeGravatar mbaruh2021-10-25-3/+0
| | | | | | | | | | | | Discussion in the pull request raised some legitimate use cases for supplying a time range for multiple channels (e.g clean the last couple of minutes instead of specifying number of messages to traverse).
| | * Update Age converter to use TZ aware datetimeGravatar mbaruh2021-10-25-1/+1
| | |
| | * Merge branch 'main' into cleanreworkGravatar mbaruh2021-10-25-221/+255
| | |\ | |_|/ |/| |
* | | Merge pull request #1908 from python-discord/fix-tz-issueGravatar Hassan Abouelela2021-10-23-2/+5
|\ \ \ | | | | | | | | Use datetime.fromtimestamp so we pass relativedelta a datetime object…
| * | | Use datetime.fromtimestamp so we pass relativedelta a datetime object, not ArrowGravatar Chris Lovering2021-10-22-2/+5
|/ / / | | | | | | | | | | | | Fixes #1907 Fixes BOT-1PA
* | | Merge pull request #1906 from python-discord/fix-tzinfo-issueGravatar Hassan Abouelela2021-10-23-2/+2
|\ \ \ | | | | | | | | Use Arrow.fromtimestamp to get an aware datetime
| * | | Use Arrow.fromtimestamp to get an aware datetimeGravatar Chris Lovering2021-10-22-2/+2
|/ / / | | | | | | | | | | | | | | | | | | Fixes #1905 Fixes BOT-1P9 datetime.fromtimestamp returned an naive datetime, so when comparing to the aware datetime from dateutil.parser.isoparse, it would raise an error.
* | | Move to timezone aware datetimes (#1895)Gravatar Boris Muratov2021-10-22-113/+122
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Move to timezone aware datetimes With the shift of the discord.py library to timezone aware datetimes, this commit changes datetimes throughout the bot to be in the UTC timezone accordingly. This has several advantages: - There's no need to discard the TZ every time the datetime of a Discord object is fetched. - Using TZ aware datetimes reduces the likelihood of silently adding bugs into the codebase (can't compare an aware datetime with a naive one). - Our DB already stores datetimes in UTC, but we've been discarding the TZ so far whenever we read from it. Specific places in the codebase continue using naive datetimes, mainly for UI purposes (for examples embed footers use naive datetimes to display local time). * Improve ISODateTime converter documentation Co-authored-by: Kieran Siek <[email protected]>
* | | Merge pull request #1904 from python-discord/modlog/explicit-thread-nameGravatar ChrisJL2021-10-22-3/+12
|\ \ \ | | | | | | | | Modlog: explicitly write thread names
| * | | Modlog: explicitly write thread namesGravatar Matteo Bertucci2021-10-22-3/+12
|/ / / | | | | | | | | | It seems like there could be some caching issue with threads causing to appear as deleted channels. Beside, we also want to keep the name of deleted threads around.
* | | Merge pull request #1902 from python-discord/bump-licensesGravatar Matteo Bertucci2021-10-21-88/+95
|\ \ \ | | | | | | | | Bumps Pip Licences
| * | | Bumps Pip LicencesGravatar Hassan Abouelela2021-10-22-88/+95
|/ / / | | | | | | | | | | | | | | | | | | Updates the pip-licences version to fix a breaking bug in the currently pinned version. Signed-off-by: Hassan Abouelela <[email protected]>
* | | Merge pull request #1897 from python-discord/modlog/correct-color-namesGravatar Karlis Suvi2021-10-20-4/+4
|\ \ \
| * | | Modlog: correct color namesGravatar Matteo Bertucci2021-10-19-4/+4
|/ / / | | | | | | Solves https://github.com/python-discord/bot/issues/1896
* | | Merge pull request #1894 from python-discord/modlog-soft-colorsGravatar ChrisJL2021-10-19-4/+4
|\ \ \ | | | | | | | | Mod-log thread: use soft colors
| * | | Mod-log thread: use soft colorsGravatar Matteo Bertucci2021-10-19-4/+4
|/ / / | | | | | | Seems like we have been using the wrong colors in mod-log.
* | | Merge pull request #1845 from python-discord/fix-sentry-BOT-1N6Gravatar Matteo Bertucci2021-10-19-6/+13
|\ \ \ | | | | | | | | Handle edge case of `message.author` being a `discord.User` when claiming a help channel.
| * \ \ Merge branch 'main' into fix-sentry-BOT-1N6Gravatar TizzySaurus2021-10-19-981/+1567
| |\ \ \ | |/ / / |/| | |
* | | | Merge pull request #1890 from python-discord/Migrate-to-socket_event_typeGravatar Matteo Bertucci2021-10-18-4/+3
|\ \ \ \ | | | | | | | | | | Migrate to on_socket_event_type event
| * | | | Migrate to on_socket_event_type eventGravatar Chris Lovering2021-10-18-4/+3
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Discord.py 2.0 (Namely this commit https://github.com/Rapptz/discord.py/commit/e2250d402e8ad035b2653eb411c8e744cc9eb3bf) removed the socket_response event, and replaced it with the socket_event_type event, which just sends the type of event triggered on the websocket. Since this event was removed, no socket stats were being incremented, as the event never triggered. I have looked through the rest of the bot, and we do not use the socket_response event type anywhere else.
* | | | Fix guild icon URL getting way in server command (#1888)Gravatar Karlis Suvi2021-10-17-1/+1
| | | |
| * | | Update log message for when author isn't `discord.Member`Gravatar Izan2021-10-19-2/+1
| | | |
| * | | Invert `isinstance` check as per reviewGravatar Izan2021-10-19-3/+6
| | | |
| * | | Add handling for when `message.author` is a `discord.User`Gravatar Izan2021-09-24-6/+11
| | | | | | | | | | | | | | | | NB: Will give a sentry warning when this happens.
| | | * Improve documentation of global variablesGravatar mbaruh2021-10-25-3/+5
| | | |
| | | * Apply requested style changesGravatar mbaruh2021-10-25-6/+4
| | | |
| | | * Adjust docstring to #1876Gravatar mbaruh2021-10-25-12/+11
| | | |
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-25 01:54:05 +0000