| Commit message (Collapse) | Author | Age | Lines |
| | |
|
| |
|
|
|
|
|
| |
Adds a check that checks if the user object is an instance of guild
member, before performing guild operations. Adds tests.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| |\
| |
| | |
General moderation improvements
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Add `build-tools` tag
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \
| | | |
| | | | |
Add myself to CODEOWNERS
|
| |/ / / |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Assuming Windows users are familiar with UAC
|
| | | | |
|
| | |\ \ |
|
| | | | |
| | | |
| | | |
| | | | |
Infoblock tag helping people install Microsoft Visual C++ Build Tools on Windows
|
| | | | | |
|
| | | | | |
|
| | |_|/
|/| | |
|
| | | | |
|
| | |/
|/| |
|
| |\ \ |
|
| | | | |
|
| | |\| |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Awaiting a done task is effectively a no-op, so it's redundant to check
if the task is done before awaiting it.
Furthermore, a task is also considered done if it was cancelled or an
exception was raised. Therefore, avoiding awaiting in such cases doesn't
allow the errors to be propagated and incorrectly allows the awaiter to
keep executing.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The channel as moved out of this category. Delete the constant too
since it isn't used anywhere else. Keep the excluded channels a tuple
to conveniently support excluding multiple channels in the future.
|
| | | |
| | |
| | |
| | |
| | | |
The import was an outlier compared to how the other modules were
imported. It's nicer to keep the imports consistent.
|
| | | |
| | |
| | |
| | |
| | | |
Some need to be shared among modules, so it became redundant to redefine
them in each module.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The event is redundant since awaiting the task accomplishes the same
thing. If the task is already done, the await will finish immediately.
If the task gets cancelled, the error is raised but discord.py suppress
it in both commands and event listeners.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Plural names imply the modules contain homogenous content. For example,
"channels" implies the module contains multiple kinds of channels.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Emoji are no longer used in channel names due to harsher rate limits
for renaming channels. Therefore, the function is obsolete.
|
| | | | |
|
| | |/
|/| |
|
| |\ \
| | |
| | |
| | |
| | | |
python-discord/sebastiaan/bugs/add-voiceban-to-scheduler-types
Add voice_ban to supported types of the infraction scheduler
|
| |/ /
| |
| |
| |
| |
| | |
The `voice_ban` infraction was not listed as a supported type for the
infraction scheduler. This meant that the scheduler did not schedule the
expiry of `voice_ban` infractions after a restart. Those unlucky users
were voice-banned perpetually.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
We will now use the deployment information located in the private
python-discord/kubernetes repository. The workflow will use a GitHub
Personal Access Token to access this private repository.
Signed-off-by: Sebastiaan Zeeff <[email protected]>
|
| | |
| |
| |
| |
| |
| |
| |
| | |
I've narrowed down repository events that trigger a Build to the "push"
event specifically. This means that we never build for a "pull request"
trigger, even if the source branch is called "master".
Signed-off-by: Sebastiaan Zeeff <[email protected]>
|
| |\ \
| |/
|/| |
Modify `!superstar` to use `apply_infraction`.
|
| | | |
|