| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
Reverse order of off-topic channels from ot0, ot1, ot2 to ot2, ot1, ot0
|
| | |
|
| |
|
| |
Put the literal converter before the Member converter so that "me"/"m" isn't attempted to be converted to a Member.
|
| |\
| |
| | |
Add support for `!infractions by <m|me|uid>`
|
| | |\
| |/
|/| |
|
| | |
| |
| | |
Co-authored-by: Xithrius <[email protected]>
|
| |\ \
| | |
| | | |
Refactor ModLog
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | | |
Filter the same kind of messages in both message deletion listeners.
|
| |/ / |
|
| | |
| |
| |
| | |
(#1937)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Don't Exit Token Filtering Early On URLs
The token filtering function would exit early if it detected a URL
within the message, but it made no extra checks to ensure there weren't
other tokens within that message that would trigger it. This made
sense when the filtering logic was written, but it's been modified since
to introduce this bug.
Regression tests included.
Signed-off-by: Hassan Abouelela <[email protected]>
* Links Advisory In Token Filter Tests
Adds a link to the advisory with reasoning for the existence of the
test.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Add sql-fstring tag
* Correct link and wording
* Correction to grammar and wording
Also adds a semicolon
* Add missing "
Co-authored-by: Bluenix <[email protected]>
Co-authored-by: TizzySaurus <[email protected]>
|
| | |
| |
| | |
Migrate to `og_blurple`
|
| |\ \
| | |
| | |
| | |
| | | |
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
|