aboutsummaryrefslogtreecommitdiffstats
path: root/tests/helpers.py (unfollow)
Commit message (Collapse)AuthorLines
2020-12-19Fix linting errorsGravatar Joe Banks-1/+0
2020-12-19Lock PipfileGravatar Joe Banks-201/+269
2020-12-19Update verification.py to use on_member_update, closes #1330Gravatar Joe Banks-27/+12
2020-12-19Bump discord.py to a unreleased refGravatar Joe Banks-1/+1
2020-12-19Install git in Docker containerGravatar Joe Banks-0/+5
2020-12-19Fix minor verification bugsGravatar Joe Banks-2/+2
2020-12-19Correctly check if the user is pendingGravatar Joe Banks-5/+6
2020-12-19Handling pending flag changes on usersGravatar Joe Banks-12/+14
2020-12-16Update verification.pyGravatar Joe Banks-2/+2
2020-12-16Add codeowner entries for ks129Gravatar ks129-1/+3
2020-12-14Fix codeblock escapeGravatar Numerlor-2/+2
On some devices the previous escaping didn't work properly, escaping all backticks will make sure none of them get registered as Markdown
2020-12-12Revert "Comma separators in metricity data in user command"Gravatar Joe Banks-2/+2
This reverts commit 628bd4ffd1717eaed9372287c59fae1b23d4cbdf.
2020-12-12Revert "Update comma code to fix tests"Gravatar Joe Banks-9/+2
This reverts commit b98c7f35916b9e5a41945030d87227394bafa1d5.
2020-12-12Update comma code to fix testsGravatar Joe Banks-2/+9
2020-12-12Comma separators in metricity data in user commandGravatar Joe Banks-2/+2
2020-12-11Single to double quotes & warning includes user ID.Gravatar Xithrius-4/+4
2020-12-11Added catching for unparsable short ISO dates.Gravatar Xithrius-4/+8
2020-12-11Make sure PR build artifact is always uploadedGravatar Sebastiaan Zeeff-1/+1
GitHub Actions has an implicit status condition, `success()`, that is added whenever an `if` condition lacks a status function check of its own. In this case, while the upload step did check for the outcome of the previous "always" step, it did not have an actual status check and, thus, only ran on success. Since we always want to upload the artifact, even if other steps failed, I've added the "always" status function now.
2020-12-10Added docstring for the user activity function.Gravatar Xithrius-1/+6
2020-12-10Slightly reformatted activity block building.Gravatar Xithrius-1/+2
Co-authored-by: Hassan Abouelela <[email protected]>
2020-12-10Compressed embed buildingGravatar Xithrius-11/+5
Co-authored-by: Hassan Abouelela <[email protected]>
2020-12-10Compressed if into or statements.Gravatar Xithrius-9/+2
2020-12-10Send a custom workflow status embed to DiscordGravatar Sebastiaan Zeeff-0/+100
This commit introduces the same custom status embed as is already being used for Sir Lancebot. The default embeds GitHub sends are disabled, as they were causing slight issues with rate limits from time to time. It works like this: - The Lint & Test workflow stores an artifact with PR information, if we are linting/testing a PR. - Whenever we reach the end of a workflow run sequence, a status embed is send with the conclusion status. Signed-off-by: Sebastiaan Zeeff <[email protected]>
2020-12-10Use Snowflake converter for snowflake commandGravatar ks129-1/+2
2020-12-09Delete verify.py, integrate `!verify` command into verification.py.Gravatar Steele-45/+16
There wasn't any reason the command needed its own cog, so the exact same functionality is now in the Verification cog.
2020-12-09Create Verify cog for new `!verify` command.Gravatar Steele-1/+46
`!verify` command allows moderators to apply the Developer role to a user. `!verify` is therefore removed as an alias for `!accept`.
2020-12-09Add sf alias to snowflake commandGravatar ks129-1/+1
2020-12-07Use the original wording of the public embed, but change the title to ↵Gravatar Steele-11/+8
"Superstarified!" Per internal staff discussion, we'll keep the wording of the message.
2020-12-06Update CODEOWNERS for @Den4200Gravatar Dennis Pham-8/+5
2020-12-06User gets a more detailed message from the botGravatar Steele-12/+16
Whereas one of my previous commits makes the message the user gets and the infraction that gets recorded the same, the recorded infraction is now shorter, but the message the user gets is more similar to the embed posted in the public channel. We also softened the language of the user-facing message a bit.