| Commit message (Collapse) | Author | Age | Lines |
| |\
| |
| | |
Fix review formatting when there's only one infraction type
|
| |/ |
|
| |\
| |
| | |
Talentpool Autoreview
|
| | |\
| | |
| | |
| | | |
into mbaruh/autoreview
|
| | | |\
| |_|/
|/| | |
|
| |\ \ \
| | | |
| | | | |
Instructions to dispute an infraction vary by infraction type.
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
python-discord/bug/info/bot-xr/code-block-null-byte
Code block: remove null bytes before parsing AST
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
python-discord/bug/info/bot-xk/defcon-threshold-none
Account for defcon threshold being None when displaying server info
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes BOT-XK
|
| |/ / / / / |
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
`ast.parse` raises a ValueError complaining that source code strings
cannot contain null bytes. It seems like they may accidentally get
pasted into Discord by users sometimes.
|
| |\ \ \ \
| | | | |
| | | | | |
Use .gitattributes to normalise line endings on check-in
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove the mixed line endings pre-commit hook because it is obsolete.
Relying on git to handle line endings means contributors have more
flexibility with which line endings they want to use on check-out.
The settings in .gitattributes only impose which line endings will
be used upon check-in (LF), which should not impact local development;
git will still respect the core.eol and core.autocrlf settings.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
* Update and rename elements.json to fruits.json
* Update _name.py
* Update _cog.py
|
| |\ \ \ \
| | | | |
| | | | | |
Simplifying the PyPi command.
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | | |
Allow the sf command to take more than one snowflake at the time
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Remove invoked command and message after failure.
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |\ \ \ \ \ \ |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | |/ / / / /
|/| | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | |\ \ \
| | |_|/ / /
| |/| | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
That style is not currently enforced by the linter.
Co-authored-by: Matteo Bertucci <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
The DM sent to infracted users now instructs them to DM modmail if they want to discuss non-ban infractions, so the tests now check if that instruction is present. Note that there already exists a superfluous test for note infractions, for which no DM is sent by design.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously, the user was instructed to email the appeals email for infraction types that don't remove one from the server. They are now instructed to DM ModMail except for Ban-type infractions. Also removed the URL string literal from the hyperlink to that URL.
|
| | | | | |/
| | | | |
| | | | |
| | | | | |
The user ID is much more accessible, and is usually what is used to obtain the nomination ID.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If it's been over a day overdue for a review, don't reschedule it.
This is done in order to not fire reviews for all nominations which
are over 30 days old when the auto-reviewing feature is merged.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This is necessary as otherwise the bot would try to review them every time it restarts
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Uncached mentions render as 'invalid' users on mobile, and with the list now showing the user's name we can now just show the ID without many problems.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | | |
Co-authored-by: ToxicKidz <[email protected]>
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It didn't make much sense for the Reviewer to subclasses Scheduler.
The Scheduler has methods that don't make sense to use on the Reviewer directly.
There is now a Scheduler object as an attribute of the Reviewer.
Interacting with it is done by adding __contains__, cancel, and cancel_all methods.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit adds the functionality to automatically review a nominee a
set number of days after being nominated.
This is implemented by subclassing the Scheduler and formatting a
review after 30 days.
The review contains details of the nominee, their nominations, the
number of messages they have and the channels they're most active in,
and statistics about their infractions and previous nominations.
Lastly, the bot will add three emojis to the review: eyes to mark as
seen, a thumbsup, and thumbsdown for the vote itself.
The code accounts for the possibility of the review being too long for
a single message but splitting it where necessary.
|