| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
| |
|
|\
| |
| | |
Forward arguments to !docs get
|
| |\
| |/
|/| |
|
|\ \
| | |
| | | |
Make `!tags edit` use PATCH to update tags
|
| |\ \
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
Split !resources into !tools and !resources.
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This splits the former !site resources into two separate commands,
one for !site resources and one for !site tools. This makes sense
now that we've split up the lists into two pages.
It also adds a new alias, !tools, to call this command.
This addresses #478.
https://github.com/python-discord/bot/issues/478
|
|\ \ \
| | | |
| | | | |
Update contrib doc for new wiki links
|
| | | |
| | | |
| | | | |
It looks silly
|
|/ / / |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
https://github.com/python-discord/bot/issues/474
This commit makes sure we're using the PATCH method to update tags,
instead of the POST method. The problem was that the `!tags edit`
command was an alias of `!tags set`, which uses the POST method to
post new tags to the API.
However, when a tag with a given name already exists, the API will
refuse a POST request in an attempt to update it; we need to use the
PATCH method to the `bot/tags/{tag_name}` endpoint instead.
I fixed this by creating a separate subcommand, `!tags edit`, that
uses the correct PATCH method to update an existing tag.
This commit closes #474
|
| | |
|
| |
| |
| | |
Co-Authored-By: S. Co1 <[email protected]>
|
|/ |
|
|\
| |
| | |
Adjust development workflow inline with new `site` changes.
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Fix help command invocation
|
| |
| |
| | |
Co-Authored-By: Mark <[email protected]>
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Anyone who is not a Rockstar, a Partner, or a member of staff
will still be redirected to #bot-commands.
|
|\ \
| | |
| | | |
Ensure docker containers are published only for master branch builds.
|
|/ / |
|
|\ \
| |/
|/| |
Update flake8-annotations & fix missing lints
|
| | |
|
|/ |
|
|\
| |
| | |
Merge infraction edit commands
|
| |\
| |/
|/| |
|
|\ \
| | |
| | | |
Minor moderation mods
|
| |\ \
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
Free Command Fix
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- For the sake of code style and consistency, the lambda has been swapped with operator.itemgetter
Signed-off-by: Daniel Brown <[email protected]>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Moved the sorted function to its own line and instead passed the generated list for code clarity.
Signed-off-by: Daniel Brown <[email protected]>
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
- Fixed bug where if two channels had the same last message timestamp the command would error out.
Signed-off-by: Daniel Brown <[email protected]>
|
| | |
| | |
| | |
| | | |
Closes #325
|
| | |
| | |
| | |
| | |
| | |
| | | |
KAIZEN!
Closes #385
|
| | |
| | |
| | |
| | | |
Closes #453
|
|/ /
| |
| |
| |
| |
| |
| | |
Add previous permanent mute invocations as aliases of their
respective mute commands.
Closes #318
|
|\ \
| | |
| | | |
Note Type Correction
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The watchchannel ABC defined its own private utility function to
format ISO datetime strings to something more human-readable. I have
removed this private utility function and replaced the calls to it
with calls to the new `format_infraction` utility function defined in
bot.utils.time.
In addition, I've changed the utility function to use `dateutil` to
parse the datetime string, since `dateutil.parser.isoparse` supports
the strings our API generates out of the box. With the built-in
`datetime.datetime.fromisoformat`, we needed to prepare the string by
slicing of the `Z` timezone indicator.
|
| | |
| | |
| | |
| | | |
The format used is %Y-%m-%d %H:%M.
|