|  | Commit message (Collapse) | Author | Age | Lines | 
|---|
| ... |  | 
| | |\ \ \ \ \ \  
| |/ / / / / /  
|/| | | | | | |  | 
| |\ \ \ \ \ \ \  
| | | | | | | | 
| | | | | | | | | Filtering: merge the word and token watch filters | 
| | |\ \ \ \ \ \ \  
| |/ / / / / / /  
|/| | | | | | | |  | 
| |\ \ \ \ \ \ \ \  
| | | | | | | | | 
| | | | | | | | | | Fixed !zen command exact word matching. | 
| | |\ \ \ \ \ \ \ \  
| |/ / / / / / / /  
|/| | | | | | | | |  | 
| |\ \ \ \ \ \ \ \ \  
| | | | | | | | | | 
| | | | | | | | | | | Logging Level Adjustments | 
| | |\ \ \ \ \ \ \ \ \  
| |/ / / / / / / / /  
|/| | | | | | | | | |  | 
| | | | | | | | | | | |  | 
| | | | | | | | | | | |  | 
| | | | | | | | | | | |  | 
| | | | | | | | | | | 
| | | | | | | | | | 
| | | | | | | | | | 
| | | | | | | | | | 
| | | | | | | | | | | With the updated definition on logging levels, there are a few events that were issuing logs at too high of a level.
This also includes some kaizening of existing log messages. | 
| | | |\ \ \ \ \ \ \ \ |  | 
| | | |\ \ \ \ \ \ \ \ \ |  | 
| | | | |\ \ \ \ \ \ \ \ \ |  | 
| | | |/ / / / / / / / / /  
| | | | | | | | | | | |   
| | | | | | | | | | | |   
| | | | | | | | | | | | | to sentence split iterate and equality check. | 
| | | | | | | | | | | | | 
| | | | | | | | | | | | 
| | | | | | | | | | | | 
| | | | | | | | | | | | | matching may not count exact word as best choice. | 
| | | | | |/ / / / / / /  
| | | | | | | | | | |   
| | | | | | | | | | |   
| | | | | | | | | | |   
| | | | | | | | | | |   
| | | | | | | | | | |   
| | | | | | | | | | |   
| | | | | | | | | | |   
| | | | | | | | | | |   
| | | | | | | | | | |   
| | | | | | | | | | | | The only difference was the automatic addition of word boundaries.
Otherwise, they shared a lot of code. The regex lists were kept separate
in the config to retain the convenience of word boundaries automatically
being added.
* Rename filter to `watch_regex`
* Expand spoilers for both words and tokens
* Ignore URLs for both words and tokens | 
| | | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | | existing function. | 
| | | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | | custom/new one. | 
| | | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | | `send_embed_with_trashcan` function. | 
| | | | | | | | | | | | |  | 
| | | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | | `send_embed_with_trashcan`, applied to docstring and to command. | 
| | | | | | | | | | | | |  | 
| | | | | | | | | | | | |  | 
| | | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | | deletion handling. | 
| | | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | | Co-Authored-By: Mark <[email protected]> | 
| | | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | 
| | | | | | | | | | | | infraction that is already expired and reason not specified. | 
| | | | | | |/ / / / / |  | 
| | | | | | | | | | | 
| | | | | | | | | | 
| | | | | | | | | | | Co-Authored-By: Mark <[email protected]> | 
| | | | | |_|/ / / /  
| | | |/| | | | |   
| | | | | | | | |   
| | | | | | | | | | Log message still used the first regex result (re.search) rather than the expanded approach (re.findall) recently added. | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | Partial hits may cause issues when packages get removed. The cache will
get bloated with packages which are no longer needed. They will keep
accumulating as more packages get removed unless the cache is unused for
7 days and gets automatically deleted by Azure Pipelines. Lingering
packages are also a potential cause for conflicts (e.g. unused package x
depends on package y==4.0 and useful package z depends on y==5.0).
Removing support for partial hits means all dependencies will be
installed whenever a single dependency changes. | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | "python" is a shorter and clearer name. | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | Prevents the following error:
Can not perform a '--user' install. User site-packages are not visible
in this virtualenv. | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | Some of pipenv's dependencies overlap with dependencies in the Pipfile.
When installing from the Pipfile, any dependencies already present in
the global site will not be installed again to the user site, and thus
will not be cached. Therefore, pipenv is installed to the user site to
ensure all dependencies get cached.
* Move PATH prepend step before pipenv invocation | 
| | | | | | | | | | |  | 
| | | | | | | | | | |  | 
| | | | | | | | | | |  | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | Reduces frequency of using pipenv to install dependencies in CI. Works
by caching the entire Python directory. Only a full cache hit will
skip the pipenv steps; a partial cache hit will still be followed by
using pipenv to install from the pipfiles.
* Disable pip cache | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | Makes the script for the coverage step cleaner. | 
| | | | | | | | | | |  | 
| | | | | | | | | | |  | 
| | | | | | | | | | |  | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | The edit causes two channel update events to dispatch simultaneously:
one for the channel topic changing and one for the category changing.
The ModLog cog currently doesn't support ignoring multiple events of
the same type for the same channel. Therefore, the ignore was hard coded
rather than using the typical ignore mechanism.
This is intended to be a temporary solution; it should be removed once
the ModLog is changed to support this situation. | 
| | | | | | | | | | |  | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | Co-Authored-By: Leon Sandøy <[email protected]> | 
| | | | | | | | | | |  | 
| | | | | | | | | | |  | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | There is no longer a reliance on static alphabetical position numbers. | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | When a channel is moved, all channels below have their positions
incremented by 1. This threw off the previous implementation which
relied on position numbers being static.
Co-authored-by: Sebastiaan Zeeff <[email protected]> | 
| | | | | | | | | | |  |