| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
| |
The site's description still stated that it was built with Flask, which
is no longer accurate due to the move to Django.
|
| |\
| |
| | |
Filtering: Implement bad words detection in nicknames
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Add cooldown channel to config-default.yml
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | | |
|
| | | |
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Converters: handle ValueError when year for duration is out of range
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \
| | | |
| | | | |
Add snekbox to the Docker compose file
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
ModLog: ignore DMs in the message delete listener
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fix AttributeError for category check
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This will provide breadcrumbs for these systems in all our Sentry
events, if applicable.
Closes #989.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Not all channels will have a category attribute. This may be fine in
production, but it does cause periodic errors when testing locally.
|
| | | | | | | |
|
| | |_|/ / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Stats: Implement rules stats
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Add staff counts to !server
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| |\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
python-discord/sebastiaan/issues/982-infraction-dm-order
Send infraction DM before applying infraction
|
| |/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
I've "reverted" the change that reversed the order of DM'ing a user
about their infraction and applying the actual infraction. A recent PR
reversed the order to stop us from sending DMs when applying the
infraction failed.
However, in order to DM a user, the bot has to share a guild with the
recipient and kicking them off of our server first does not help with
that. That's why I reverted the change and reverted some other minor
changes made in relation to this change.
Note: I did not change the code sending the DM itself; I merely moved it
back to where it belongs and added a comment about the necessity of
doing the DM'ing first.
I couldn't cleanly revert a commit to do this, as changes were spread
out over and included in multiple commits that also contained changes
not related to the `DM->apply infraction` order.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Add the !modmail tag
|
| |/ / / / / / |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Remove all sending of avatar_hash
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Add multichannel !purge
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This ensures that only what was actually deleted will be uploaded.
I managed to get a 400 response from our API when purging twice in
quick succession. Searching the history manually for these messages is
unreliable cause of some sort of race condition.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
We're removing the context manager due to async concerns, so we'll go
back to the old approach again of ignoring specific messages and
iterating history.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This reverts commit 0737b1a6
This isn't gonna work, because async is a thing.
|
| | |\ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This command was written to support only a single channel, and with the
move to multi-channel purges, we need to rethink the way the invocation
deletion happens. We may be invoking this command from a completely
different channel, so we can't necessarily look inside the channels
we're targeting for the invocation.
So, we're solving this by just deleting the invocation by using
ctx.message. We do this before we start iterating message history, and
then we only need to iterate the number of messages that was passed into
the command.
A much cleaner approach, which solves the bug reported and identified by
@MarkKoz.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This new context manager makes it easier to make the mod_log ignore
actions like message deletions. The only existing method is the
`ignore()` method, which requires that you pass all the messages you
want to ignore into it.
This one just ignores everything inside its scope.
This isn't the DRYest approach, but it's low-cost and improves the
readability of clean.py quite a bit. Ideally we should go through and
give modlog a proper cleanup, because it's kinda ugly right now.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Thanks @MarkKoz!
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Co-authored-by: Mark <[email protected]>
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
We can now pass in as many channel mentions as we want after any !purge
command - for example `!purge all 5 #python-general #python-language`
|
| | | |\ \ \ \ \ \
| |_|/ / / / / /
|/| | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This is a companion commit to this PR:
https://github.com/python-discord/site/pull/356
This PR must be merged before this commit.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This also changes a few aesthetic problems pointed out in review by
@MarkKoz and @kwzrd.
|
| | | | |\ \ \ \ \
| |_|_|/ / / / /
|/| | | | | | | |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Link #how-to-get-help in !free tag
|