| Commit message (Collapse) | Author | Age | Lines |
| |\
| |
| | |
Better handle native gated users
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| | |
Remove selenium from the element list
|
| | |\
| |/
|/| |
|
| | | |
|
| |\ \
| | |
| | | |
Fix backtick escapes in the codeblock tag
|
| |/ /
| |
| |
| |
| | |
On some devices the previous escaping didn't work properly, escaping
all backticks will make sure none of them get registered as Markdown
|
| | |
| |
| |
| | |
This reverts commit 628bd4ffd1717eaed9372287c59fae1b23d4cbdf.
|
| | |
| |
| |
| | |
This reverts commit b98c7f35916b9e5a41945030d87227394bafa1d5.
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | |\ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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]>
|
| |\ \ \
| | | |
| | | | |
Create command for showing Discord snowflake creation time
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
New `!verify` command to manually apply the Developer role
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Relay the moderator's reason for `!superstarify` to the user
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
`!close` removes the cooldown role from the claimant
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | |\ \ \ \ \ \ |
|
| | | | | | | | | |
|
| | |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Stelercus/close_command
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Previously `!close` would remove the cooldown role from the person who issued the command, whereas now `unclaim_channel` handles removing the role from the claimant if it was their only channel open.
|
| | |\ \ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Stelercus/close_command
|
| | | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Deleted expensive logging operation; moved cooldown role removal functionality to new `unclaim_channel` method; handle possibility that claimant has left the guild; optimized redis cache iteration with `any`
|
| | |\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
Stelercus/close_command
|
| | | | | | | | | | | | | |
|
| | | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
fixed so role is removed when the channel times out
|
| | | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
someone else; flattened `close_command`
|
| | | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
"Superstarified!"
Per internal staff discussion, we'll keep the wording of the message.
|
| | | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
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.
|
| | | | | | | | |\ \ \ \ \
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
swfarnsworth/superstar
|
| | | | | | | | | | | | | | |
|
| | | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
Previously, the infraction DM from the bot gave a formulaic message about the nickname policy. It now gives a slightly different message along with the reason given by the mod. This means that the message the user gets and the infraction reason that gets recorded are now the same.
|
| | | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
There wasn't any reason the command needed its own cog, so the exact
same functionality is now in the Verification cog.
|
| | |_|_|_|_|_|_|_|/ / / /
|/| | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
`!verify` command allows moderators to apply the Developer role to a
user. `!verify` is therefore removed as an alias for `!accept`.
|
| | | | | | | | | | | | | |
|
| | |_|_|_|_|_|_|/ / / /
|/| | | | | | | | | | |
|
| | |_|_|_|_|_|/ / / /
|/| | | | | | | | | |
|
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|