| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
python-discord/consider-parent-channels-when-checking-mod-channels
Consider parent channels when checking mod channels
|
| |/ / / / / |
|
| |\ \ \ \ \ |
|
| |/ / / / /
| | | | |
| | | | |
| | | | | |
Move text from footer to description.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Clean Cog Rework
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Unpin All Messages When Moving Help Channels
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | | |
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!
|
| | |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
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).
|
| | | | | | | |
|
| | | |\ \ \ \
| |_|/ / / /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
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]>
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | |\ \ \ |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Added a cog_command_error method that sets cleaning to False when a command ends on an exception.
I don't have anything in mind that might cause this, but it will ensure that in any case the cog will still be usable.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Handle cases where there are no enclosing backticks, and where the regex pattern is invalid.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
When providing a user ID it would clash with `traverse` which came first.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In case of old messages, it would delete the old messages first, and only then bulk delete the remainder, which affected logging.
This commit corrects the deletion order.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Tells the user if clean cancel was attempted with no ongoing clean.
- Fixes MaxConcurrencyReached call bug. There was a missing argument, and it shouldn't invoke the help embed anyway, so it's now a message.
- Some code refactoring.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The regex was lowercased, even though regex patterns are case sensitive.
Also adds the DOTALL flag.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Co-authored-by: Shivansh-007 <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
After discussion, backticks seems like the preferrable formatting as it also cancels Discord's formatting.
Additionally removed the Optionals from the last args in the commands, to not silently ignore incorrect input.
|