aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
| | | | | * Better check way of checking timelapsGravatar kraktus2019-10-11-11/+13
| | | | | | | | | | | | | | | | | | | | | | | | Use a coroutine instead of a list.
| | | | | * Requested changesGravatar kraktus2019-10-05-7/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changed `PERIODIC_PING` from 2 f-string to one normal and one f-string. The bot now checks in the lasts 5 messages (why 5? Admins/mods could have add some notes, and/or users could have wrong taped the command, which lead the bot to send a message) the time of his last ping. If there is not historic ping, will send one (initialization and make the command more robust). If there is one previous `PERIODIC_PING` message, checks if it older than one week. I also set the countdown from 1 to 12 hours. Why not more? Because each time the bot is restarted the countdown is reset to 0, and I don't know how often it is restarted.
| | | | | * Added a new `periodic_ping` to fix #320Gravatar kraktus2019-10-05-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | Created a new function named `periodic_ping` in `verification.py`, using `discord.ext.tasks` and `datetime` module. Every hour the function checks if the last message in the channel (ie last message of the bot) is older than a week. If so, it deletes this message and post a new one.
| | | | | * Added to the .gitignore file a new file to be ignored, .DS_Store (only on ↵Gravatar kraktus2019-10-05-0/+3
| |_|_|_|/ |/| | | | | | | | | | | | | | Mac OS), that stores custom attributes of its containing folder. New contributors on Mac OS won't have to bother anymore about this mysterious file that create when you fork the project.
* | | | | Merge pull request #481 from bendiller/fetch_posts_retriesGravatar S. Co12019-10-03-15/+24
|\ \ \ \ \ | |_|_|_|/ |/| | | | Add checks for valid response and retries to fetch_posts()
| * | | | Merge branch 'master' into fetch_posts_retriesGravatar Mark2019-10-03-23/+106
| |\ \ \ \ | |/ / / / |/| | | |
* | | | | Merge pull request #486 from python-discord/mute-fixGravatar Joseph2019-10-03-5/+42
|\ \ \ \ \ | | | | | | | | | | | | Fix mutes not being re-applied on rejoins.
| * \ \ \ \ Merge branch 'master' into mute-fixGravatar Joseph2019-10-03-1/+1
| |\ \ \ \ \ | |/ / / / / |/| | | | |
* | | | | | Merge pull request #483 from python-discord/fix-watchchannels-unload-cog-bugGravatar S. Co12019-10-02-1/+1
|\ \ \ \ \ \ | | | | | | | | | | | | | | Fix `cog_unload` bug in WatchChannel ABC
| * \ \ \ \ \ Merge branch 'master' into fix-watchchannels-unload-cog-bugGravatar S. Co12019-10-02-7/+36
| |\ \ \ \ \ \ | |/ / / / / / |/| | | | | |
| * | | | | | Fix `cog_unload` bug in WatchChannel ABCGravatar Sebastiaan Zeeff2019-10-02-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://github.com/python-discord/bot/issues/482 There was small bug in the `cog_unload` method of the WatchChannel ABC in `bot.cogs.watchchannels.watchchannel`. The problem was that it tries to check if the Task assigned to `self._consume_task` is done by accessing its `done` method. However, if a watch channel has not yet relayed messages after the bot has started, it will not have a consumption task yet, meaning this `_consume_task` attribute will be assigned to `None`. The solution is to change the `if` condition to: `if self._consume_task and not self._consume_task.done():` This commit closes #482
| | * | | | | Fix mutes not being re-applied on rejoins.Gravatar scragly2019-10-03-5/+42
| |/ / / / / |/| | | | |
* | | | | | Merge pull request #467 from Ayplow/short-docsGravatar Mark2019-10-01-5/+5
|\ \ \ \ \ \ | | | | | | | | | | | | | | Forward arguments to !docs get
| * \ \ \ \ \ Merge branch 'master' into short-docsGravatar Mark2019-10-01-12/+58
| |\ \ \ \ \ \ | |/ / / / / / |/| | | | | |
* | | | | | | Merge pull request #475 from python-discord/fix-tags-edit-commandGravatar Mark2019-10-01-2/+31
|\ \ \ \ \ \ \ | |_|/ / / / / |/| | | | | | Make `!tags edit` use PATCH to update tags
| * | | | | | Merge branch 'master' into fix-tags-edit-commandGravatar Mark2019-10-01-10/+27
| |\ \ \ \ \ \ | |/ / / / / / |/| | | | | |
* | | | | | | Merge pull request #480 from python-discord/separate_tools_and_resourcesGravatar Mark2019-10-01-7/+24
|\ \ \ \ \ \ \ | |_|_|_|_|_|/ |/| | | | | | Split !resources into !tools and !resources.
| * | | | | | Fix missing type annotations and docstring errors.Gravatar Leon Sandøy2019-10-01-7/+3
| | | | | | |
| * | | | | | Create !tools alias and split !site resources.Gravatar Leon Sandøy2019-10-01-7/+28
|/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 (#470)Gravatar scragly2019-10-02-3/+3
|\ \ \ \ \ \ | |_|_|_|/ / |/| | | | | Update contrib doc for new wiki links
| * | | | | Remove single-item listGravatar S. Co12019-10-01-2/+1
| | | | | | | | | | | | | | | | | | It looks silly
| * | | | | Update contrib doc for new wiki linksGravatar sco12019-09-30-3/+4
|/ / / / /
| * / / / Make `!tags edit` use PATCH to update tagsGravatar Sebastiaan Zeeff2019-10-01-2/+31
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | Update docs cog docstring & fix URL converter attribute errorGravatar S. Co12019-10-01-4/+4
| | | |
| * | | Update bot/cogs/doc.pyGravatar Ayplo2019-10-01-1/+1
| | | | | | | | | | | | Co-Authored-By: S. Co1 <[email protected]>
| * | | Forward arguments to getGravatar Tom Sputz2019-09-30-1/+1
|/ / /
| * | Improve readabilityGravatar Ben Diller2019-10-03-0/+1
| | | | | | | | | Co-Authored-By: Mark <[email protected]>
| * | Move asyncio.sleep() to avoid disturbing function signatures.Gravatar bendiller2019-10-03-16/+13
| | |
| * | Add sleep(3) between retries, with bot indicating typing during sleepGravatar bendiller2019-10-02-4/+9
| | |
| * | Add logging for invalid response (after all retries are exhausted)Gravatar bendiller2019-10-02-1/+3
| | |
| * | Add checks for valid response and retries to fetch_posts()Gravatar bendiller2019-10-01-9/+13
|/ /
* | Adjust development workflow inline with new `site` changes. (#464)Gravatar scragly2019-09-30-13/+28
|\ \ | | | | | | Adjust development workflow inline with new `site` changes.
| * | Remove temp instructions, add link to contrib guide on website.Gravatar scragly2019-09-30-27/+1
| | |
| * | Make `bot` wait for `web`, use `latest` web image.Gravatar scragly2019-09-30-2/+3
| | |
| * | Do up some basic setup instructions for new setup.Gravatar scragly2019-09-29-0/+28
| | |
| * | Update site to use new manage.py, add bot dev compose.Gravatar scragly2019-09-28-7/+20
| | |
| * | Use pathlib, avoid inner `bot` directory for logs.Gravatar scragly2019-09-28-7/+6
|/ /
* | Merge pull request #460 from python-discord/help-fixGravatar scragly2019-09-28-4/+4
|\ \ | | | | | | Fix help command invocation
| * | Apply suggestions from code reviewGravatar S. Co12019-09-27-2/+2
| | | | | | | | | Co-Authored-By: Mark <[email protected]>
| * | Use Command.cog_name attr instead of missing instance attrGravatar S. Co12019-09-26-2/+2
| | |
| * | Fix incorrect kwargs in watchchannel modlog sendGravatar S. Co12019-09-26-2/+2
| | |
* | | Lovely lemon let loose and forgot linting.Gravatar scragly2019-09-28-1/+1
| | |
* | | Allow Rockstars and Partners to use !eval.Gravatar Leon Sandøy2019-09-27-7/+10
| | | | | | | | | | | | | | | 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 bu… (#463)Gravatar scragly2019-09-27-1/+1
|\ \ \ | | | | | | | | Ensure docker containers are published only for master branch builds.
| * | | Ensure docker containers are published only for master branch builds.Gravatar scragly2019-09-27-1/+1
|/ / /
* | | Update flake8-annotations & fix missing lints (#461)Gravatar scragly2019-09-27-10/+45
|\ \ \ | |/ / |/| | Update flake8-annotations & fix missing lints
| * | Remove invalid colorama markersGravatar S. Co12019-09-26-2/+0
| | |
| * | Update flake8-annotations & fix missing lintsGravatar S. Co12019-09-26-10/+47
|/ /
* | Merge pull request #457 from python-discord/infraction-edit-mergeGravatar S. Co12019-09-26-157/+91
|\ \ | | | | | | Merge infraction edit commands
| * \ Merge remote-tracking branch 'origin/master' into infraction-edit-mergeGravatar MarkKoz2019-09-26-148/+19
| |\ \ | |/ / |/| |
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-23 11:18:09 +0000