| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
| |
The usage of 127462 as a unicode start point isn't super clear for
other devs coming across the code in future, so assigning it to a nicely
named variable with an accompanying inline comment should help make
things clearer.
|
| |
|
|
|
| |
If the vote command receives less than 2 options, it's not being used
for it's intended usage and is considered a user input error.
|
| |\ |
|
| | |\
| | |
| | | |
Fix filtered extension string out of scope for antismalware log message
|
| | | |\
| | |/
| |/| |
|
| | | |
| | |
| | | |
* Fix typo in file extensions list comprehension
|
| |/ /
| |
| |
| |
| |
| | |
The vote command takes a given list of options and generates a simple
message and corresponding reactions for each so members can quickly take
a vote on a subject during in-server discussions and meetings.
|
| |\ \
| |/
|/|
| |
| | |
python-discord/tag-search-searches-tags-via-content-instead-of-names
Subcommand `search` and `search any` to search inside tags' contents and not names.
|
| | |
| |
| |
| |
| |
| | |
- Split `_get_tags_via_content` - introduce `_send_matching_tags`
- `_send_matching_tags` will send and paginate like `!tag`
- Simplified `is_plural` even more.
|
| | |
| |
| | |
Co-Authored-By: Mark <[email protected]>
|
| | |
| |
| |
| |
| |
| |
| | |
- Show the process of sanitizing the List[str] `keywords_processed`.
- Show the process of finding tag for `matching_tags` ( was `founds` ).
- Refactored the logic to find boolean `is_plural`.
- Minor wording changes for docstring.
|
| | |
| |
| |
| |
| |
| |
| | |
multiple tags are found.
- Added a truthy check for each `query` since `','.split()` returns a list of two empty strings.
- Changed from `Did you mean ...` to `Here are the tags containing the given keyword(s):` to be much more descriptive about the results - they are `tag` and not `term` to be searched.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- Refactored `if` block - change to only send result when there is any result.
- Added better type hinting for `check` argument of `_get_tags_via_content` - changed from `callable` to `Callable[[Iterable], bool]`.
Thanks to @markkoz 's reviews
Co-Authored-By: Mark <[email protected]>
|
| |/
|
|
|
|
|
| |
instead of names
- `!tag search` will search for multiple keywords, separated by comma, and return tags that has ALL of these keywords.
` !tag search any` is the same as `!tag search` but it return tags that has ANY of the keyword instead.
|
| |\
| |
| | |
Pre-commit tweaks
|
| | |
| |
| |
| |
| |
| | |
It was excluding files that are already ignored by git. Pre-commit
respects git ignore, even with --all-files, so these ignores were
redundant.
|
| |/
|
|
|
|
| |
It's noisy, messy output. It's not of much benefit anyway as users can
run git diff locally if they really need to see a diff. They have to do
work locally anyway since CI won't commit the fixes pre-commit makes.
|
| |\
| |
| | |
implement !zen command.
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Added Pagination to !roles command
|
| | |\ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | | |
role(s)" due changes in command.
|
| | | |
| | |
| | |
| | | |
is more then 1 role.
|
| | | | |
|
| | | | |
|
| | |\ \ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
title (was before in footer).
|
| | | | | |
|
| | | | | |
|
| | | | |\
| |_|_|/
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Expand Antimalware User Feedback & Logging
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
python-discord/extensions-cog-docstring-deprecation-warning
Use raw strings for docstrings with forward slashes
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Add more pre-commit hooks and run them in CI
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | | |
This was added by the now-removed Snake cog & is not used elsewhere on bot.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The mock gets used by the flake8 pre-commit hook, which invokes flake8
via `pipenv run flake8`. It's normally useful to use pipenv here cause
it ensures flake8 is invoked within the context of the venv. However, in
CI, there is no venv - dependencies are installed directly to the
system site-packages. `pipenv run` does not work in such case because it
tries to create a new venv if one doesn't exist (it doesn't consider the
system interpreter to be a venv).
This workaround (okay, it's a hack) creates an executable shell script
which replaces the original pipenv binary. The shell script simply
ignores the first argument (i.e. ignores `run` in `pipenv run`) and
executes the rest of the arguments as a command. It essentially makes
`pipenv run flake8` equivalent to just having ran `flake8`. When
pre-commit executes pipenv, the aforementioned script is what will run.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
A cache for an outdated pre-commit environment may still be useful. It
may be the case that only some hooks need to be updated rather than
all.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* Remove trailing whitespaces
* Specify error code for a noqa in the free command
|
| | |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
A few docstrings in `bot.cogs.extensions` have forward slashed in them to escape Markdown rendering when our help feature uses these docstring in a Discord message. However, the use of forward slashes with an invalid escape sequence in docstrings now raises a DeprecationWarning in Python:
/home/sebastiaan/pydis/repositories/bot/bot/cogs/extensions.py:72: DeprecationWarning: invalid escape sequence \*
PEP 257 (Docstring Conventions, https://www.python.org/dev/peps/pep-0257/) states that raw strings should be used for docstrings that use forward slashes, so I've added the `r`-prefix to the docstrings that use forward slashes.
|
| |\ \ \ \ \ \
| |_|_|_|/ /
|/| | | | | |
Prevent exception if a watched user sends a DM to the bot
|
| |/ / / / /
| | | | |
| | | | | |
The previous embed assumed that the messages would be sent on the server, where the channel would have a name and the message would have a jump URL. For a DM, neither of these are present and an exception will be raised when attempting to construct the embed for the webhook to send.
|
| | | |\ \ \
| |_|/ / /
|/| | | | |
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
Create AsyncResolver inside a coroutine to avoid DeprecationWarning
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|