| Commit message (Collapse) | Author | Age | Lines |
| | |
|
| |
|
|
| |
(Help command uses docstrings, so make them user-friendly)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Revert "Rename some variables"
This reverts commit 2f5aeb06e816240b08453b5cf327c6b77958a3ab.
Fix variable names (again)
And again
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| | |
https://github.com/mathstrains21/bot into patreon
|
| | |\ |
|
| | | |
| | |
| | | |
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.
|
| | | |\
| | | |
| | | | |
Filtering: add autoban on specific reasons
|
| | | | |
| | | |
| | | | |
Co-authored-by: ChrisJL <[email protected]>
|
| | | | |
| | | |
| | | | |
Co-authored-by: ChrisJL <[email protected]>
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |\
| | | |/
| | |/| |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | | |
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!
|
| |/ / / |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Add function to send the current supporters
Add a command to call this function
|
| |\| | |
|
| | |\ \
| | | |
| | | | |
Use datetime.fromtimestamp so we pass relativedelta a datetime object…
|
| | |/ /
| | |
| | |
| | |
| | | |
Fixes #1907
Fixes BOT-1PA
|
| | |\ \
| | | |
| | | | |
Use Arrow.fromtimestamp to get an aware datetime
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
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]>
|
| | |\ \
| | | |
| | | | |
Modlog: explicitly write thread names
|
| | |/ /
| | |
| | |
| | | |
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.
|
| | |\ \
| | | |
| | | | |
Bumps Pip Licences
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |\ \
| | | |
| | | | |
Mod-log thread: use soft colors
|
| | |/ /
| | |
| | | |
Seems like we have been using the wrong colors in mod-log.
|
| | |\ \
| | | |
| | | | |
Handle edge case of `message.author` being a `discord.User` when claiming a help channel.
|
| | | |\ \
| | |/ /
| |/| | |
|