| Commit message (Collapse) | Author | Lines |
|
Move text from footer to description.
|
|
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.
|
|
Co-authored-by: ChrisJL <[email protected]>
|
|
Co-authored-by: ChrisJL <[email protected]>
|
|
|
|
|
|
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).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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]>
|
|
Fixes #1907
Fixes BOT-1PA
|
|
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
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]>
|
|
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.
|
|
Updates the pip-licences version to fix a breaking bug in the currently
pinned version.
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
Solves https://github.com/python-discord/bot/issues/1896
|
|
Seems like we have been using the wrong colors in mod-log.
|
|
|
|
|
|
Co-authored-by: Boris Muratov <[email protected]>
|
|
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!
|
|
|
|
|
|
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.
|
|
|
|
Fixes #1886
Fixes BOT-1NZ
This was updated with Discord.py 2.0.
|
|
Fixes #1884
Fixes BOT-1NY
Discord.py 2.0 changed how this works, webhooks now look for the MISSING sentinal, rather than None to determine whether files are being passed.
This was updated in this commit: https://github.com/Rapptz/discord.py/commit/a6f7213c89e9d592c69ea3c631b0cb2bdab19577
|
|
Fixes #1881
Fixes BOT-1NX
|
|
* Run debug log before help command invocation to avoid delayed logs
* Refactored other areas of code slightly, ensuring logging is done as soon as possible. Removed outdated comment
* Ensured debug logs were sent for disabled commands
Co-authored-by: Xithrius <[email protected]>
|
|
* Regex: add a word boundary before .gg and use named groups
Before this commit, `an-arbitrary-domain.gg/notaninvite` would trigger the filter.
This solve the issue by adding a word boundary before this branch of the pattern.
* Regex: replace the word boundary by a word char
Co-authored-by: ChrisJL <[email protected]>
Co-authored-by: ChrisJL <[email protected]>
Co-authored-by: Xithrius <[email protected]>
|
|
Since channels that mods can't read are now implicitly ignored, there is no need to explicitly ignore them.
|
|
|
|
This new name better describes what this function actually does
|
|
The main purpose of this is so that we don't need to keep adding to the modlog_blacklist for every new channel we want to ignore, since it now implicitly ignores channels mods don't have read perms to.
This is done by making use of Discord.py 2.0's updated behaviour of Channel.permissions_for() where it can now accept a role and determines the permissions of users in that role for a given channel. This takes into account default permissions as well as channel overrides.
Co-authored-by: Xithrius <[email protected]>
|
|
Closes #1232
Modifies the docstring sent for per-command help to remove weird formatting issues mentioned in #1232. Removes newlines that are not used for paragraph breaks, after retrieving the docstring, and lets the embed handle it on the discord side.
Allow overriding this behaviour via \u2003 to denote a non-escapable break.
Co-authored-by: Hassan Abouelela <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There's now always one blank line (no more, no less) after an import
|
|
|