aboutsummaryrefslogtreecommitdiffstats
path: root/tests/conftest.py (unfollow)
Commit message (Collapse)AuthorLines
2019-10-14Implement a bypassable cooldown decoratorGravatar Ava-3/+50
2019-10-14Add Reddit OAuth tasks and refactor codeGravatar Jens-6/+76
2019-10-13Update utils.pyGravatar larswijn-1/+1
Switch around trying order (txt first, then rst)
2019-10-12Utilize __str__ of discord.Member in logging and outputGravatar kosayoda-47/+33
2019-10-12Use `bot.utils.humanize_delta`, tidy bot response, remove stray f from f-stringGravatar mathsman5133-15/+5
2019-10-12Raise `ValueError` on negative `max_units`.Gravatar Johannes Christ-3/+9
2019-10-11Get the prefix from the config for the periodic ping messageGravatar MarkKoz-2/+2
2019-10-12Bump the site PostgreSQL version to 12.Gravatar Johannes Christ-1/+1
2019-10-11Check that the periodic ping author is the botGravatar MarkKoz-1/+1
2019-10-11Revise comments and the doctsring for the periodic ping functionGravatar MarkKoz-7/+10
2019-10-11Cancel the periodic ping task when the verification cog is unloadedGravatar MarkKoz-0/+4
2019-10-11Better check way of checking timelapsGravatar kraktus-11/+13
Use a coroutine instead of a list.
2019-10-11Add typehints.Gravatar Johannes Christ-3/+2
2019-10-11Small code review fixesGravatar Ava-3/+2
2019-10-11Implement test cases suggested by @MarkKoz.Gravatar Johannes Christ-0/+11
2019-10-11Log member_ban event to #user-logGravatar kosayoda-3/+2
2019-10-11Add !otn forceadd command.Gravatar kosayoda-0/+8
2019-10-11Add check to !otn add to prevent too similar names.Gravatar kosayoda-2/+24
2019-10-09Resolve #458: support exact timestamps as args for mod commandsGravatar MarkKoz-22/+43
* Rename all parameters to "duration" for consistency * Add missing docs about duration parameter to the superstarify command
2019-10-09Resolve #357: show ban reason and bb watch status in unban mod logGravatar MarkKoz-1/+18
2019-10-09Fix #346: display infraction count after giving an infractionGravatar MarkKoz-3/+10
2019-10-09Show help when ext load/unload are invoked without argumentsGravatar MarkKoz-0/+8
2019-10-09Add Reddit OAuth tasks and refactor codeGravatar Jens-6/+77
2019-10-08Expand token detection regex character exclusionGravatar sco1-5/+5
This helps enable broader detection of tokens being used in contexts beyond simple assignment
2019-10-08Ensure display name changes are loggedGravatar Sebastiaan Zeeff-1/+6
https://github.com/python-discord/bot/issues/489 Recently, we discovered that not all display name changes were logged to the #user-log channel. This problem was caused by the `old_value` or the `new_value` showing up as `None` when a user sets or removes a guild-specific nickname. Since we ignore changes where one of the two values is `None`, we did not log these `None->nick` or `nick->None` events. Since we are mainly interested in the display name of the user, and the display name is equal to the user's guild-specific nickname if they have set one and otherwise their username, I made the following changes: - Add logging of changes in the display names of members. - Ignore nick-specific changes completely, since these changes are already captured by the changes in the display name we now log. This closes #489
2019-10-08Fix linting errorsGravatar Ava-7/+8
2019-10-08Show infraction reason when the bot is the actorGravatar Sebastiaan Zeeff-1/+5
https://github.com/python-discord/bot/issues/476 We recently decided to hide the reason in the confirmation message the bot sends after applying an infraction. In most situations, this makes sense, since the message containing the invocation command already contains the reason. However, if the infraction was triggered by the bot itself (e.g., an antispam trigger), this means that we're missing information that provides context to the infraction. This commit adds the reason back to the confirmation message, but only if the actor of the infraction was the bot itself. Closes #476
2019-10-08Fix wrong importGravatar Ava-2/+1
2019-10-08Add raw commandGravatar Ava-3/+83
Closes #334
2019-10-08Set bot as actor of antispam infractionsGravatar Sebastiaan Zeeff-1/+3
As mentioned in #476, the bot currently sets the actor of infractions applied due to an antispam rule trigger to the offending member. The reason is that we get a `Context` object from the message that triggered the antispam rule, which was sent by the offender. I've changed it by patching both available author attributes, `Context.author` and `Context.message.author` with the bot user.
2019-10-07Only allow members currently in the guild to be warnedGravatar MarkKoz-1/+1
2019-10-07Update the nickname policy URLGravatar Mark-1/+1
Co-Authored-By: Sebastiaan Zeeff <[email protected]>
2019-10-07Escape asterisks in extensions docstringsGravatar MarkKoz-7/+7
2019-10-07Support wildcards and multiple extensions for load and unload commandsGravatar MarkKoz-36/+48
* Rename batch_reload() to batch_manage() and make it accept an action as a parameter so that it can be a generic function. * Switch parameter order for manage() to make it consistent with batch_manage(). * Always call batch_manage() and make it defer to manage() when only 1 extension is given. * Make batch_manage() a regular method instead of a coroutine.
2019-10-07Use quotes instead of back ticks around asterisk in docstringsGravatar MarkKoz-4/+4
2019-10-07Add missing awaits and call bot as attributGravatar Jens-14/+14
2019-10-06Update max threshold for attachmentsGravatar Derek-1/+1
2019-10-06Update !mentionGravatar mathsman5133-14/+21
- Lock the role if the message wait has timed out - Sleep, lock role and send notification if mention by staff member found. - Lock role and send notification if mention by non-staff member found.
2019-10-05Requested changesGravatar kraktus-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.
2019-10-05Added a new `periodic_ping` to fix #320Gravatar kraktus-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.
2019-10-05fix linterGravatar mathsman5133-1/+2
2019-10-05properly send message with `asyncio.run`Gravatar mathsman5133-3/+7
2019-10-05add requested changes for reviewGravatar mathsman5133-15/+28
2019-10-05Specify names of "prepare_cog" methodsGravatar Jens-19/+19
2019-10-05revert back `tests.cogs.test_information`. I got them in the wrong order...Gravatar mathsman5133-2/+2
2019-10-05revert back `tests.cogs.test_information`Gravatar mathsman5133-3/+4
2019-10-05Added to the .gitignore file a new file to be ignored, .DS_Store (only on ↵Gravatar kraktus-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.
2019-10-05Create the !mention commandGravatar mathsman5133-8/+47
2019-10-04Make categories class attributes and support descriptionsGravatar MarkKoz-5/+20
* Document support for custom categories.
2019-10-04Fix error when symbol_id cannot be found in doc HTMLGravatar MarkKoz-0/+3
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-29 11:29:01 +0000