| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Since the Discord.py repository has been archived, we can switch to the latest commit of 2.0a0, knowing no breaking change will occur (still pinned to the commit just in case).
This commits fixes any problem related to the migration:
- New avatar interface
- TZ aware datetimes
- Various inernal API changes
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Some doc symbols are improperly generated and never exist on the doc page
the inventory file defines them in, causing the stale warning to get raised
every time the page is parsed (at a maximum every week because of the redis
expire).
This can be prevented by keeping a counter in redis for the items which were
stale, every time the item is warned for the counter is incremented and set to
expire in 3 weeks.
Then a warning is only raised when the counter is below 3, resulting in the
unpreventable warning only being raised twice until it is fixed by the
maintainers after it expires in 3 weeks after the last increment.
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | |_|_|_|_|_|/ /
|/| | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This is a new appeals process we are trialing. Users who get banned join this server and DM a modmail bot, who relays the message to the main server for mods to discuss.
I have updated the shortening logic to allow for extra information to be included at the end of the embed, while still staying under the limit.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | |_|_|_|_|_|/
|/| | | | | |
| | | | | | |
| | | | | | | |
NB: Will give a sentry warning when this happens.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Update paste-site URL in `!paste`
|
| |/ / / / / / / |
|
| |\ \ \ \ \ \ \
| |_|_|_|/ / /
|/| | | | | | |
Add `cog` as an alias to extensions command
|
| |/ / / / / / |
|
| |\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Add metricity to docker-compose
|
| | | | | | | |
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
By adding metricity to the compose, we allow it to migrate itself, rather than needing the site to do it.
Defaulting 'USE_METRICITY' to false means that it will run migrations, but not actually start the bot. This means we don't add another service that needs to run all the time, which could impact some contribs on lower powered hardware.
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
Adds Core Dev Voting To Changelog Blacklist
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds the channel used for voting on contributors to the message
changelog blacklist.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
python-discord/Only-check-domain-filters-against-URL-like-parts-of-a-message
Only check URL-like objects against domain filters
|
| | |\ \ \ \
| |/ / / /
|/| | | |
| | | | | |
Only-check-domain-filters-against-URL-like-parts-of-a-message
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Add string-formatting tag
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Declare TalentPool.cache on init of cog
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This raised questions from helpers when they saw that someone had many previous nominations. There is no reason why a helper needs to see this information.
|
| | | | | | | | |
|
| | | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This avoids issues in the server cog trying to access it before it's assigned and refreshed.
I also migrated to the tasks to `scheduling.create_task()` as the created tasks currently don't have any error handling they can hide errors in development until the task object is destroyed (if that occurs at all) which logs the exception. The scheduling alternative attaches a callback which logs exceptions to prevent this.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
After some discussion back and forth, I've adjusted how to display
the examples and code bock to be of a more REPL-style.
Additionally, a filler character for the "Center Me!" string is added to
illustrate how exactly in centers it.
This commit also adds some small styling changes.
|
| | | | | | | |
|
| | |/ / / /
|/| | | |
| | | | |
| | | | | |
Adds a tag to show the string formatting mini language
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Add support for `!infraction last`
`!infraction last` will view details of the last infraction the user made. Also changes the `Infraction` converter to use the `expanded` endpoint
1) Added `InvalidInfraction` to `bot.errors` - called when value passed to `Infraction` converter is invalid
2) Improved error messages for when an invalid infraction is passed to `!infraction {infr_id}`
3) Improved some other messages/docstrings etc.
Co-authored-by: Xithrius <[email protected]>
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
Add .gg/ to invite filter regex
|
| |/ / / / |
|
| | | | |
| | | |
| | | |
| | | | |
This was attr changed when we removed the concept of a user being 'watched' while
removing the talentpool.
|
| |\ \ \ \
| | | | |
| | | | | |
Pin platform in Dockerfile
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Add concurrency rules to all GitHub workflows
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This concurrency rule means that workflow actions will be cancelled if a new set of actions are triggered on the same ref. A ref is either a PR or a branch itself.
Doing this means that if someone pushes to a PR multiple times in quick succession, workflows won't get queued up. Instead, only the workflows from the most recent changes will run, as this is all we really care about anyway.
I see the benefits of this as twofold.
1. The author gets faster feedback about the most recent change pushed, rather than have to wait for all previous runs to completed
2. Other contributors don't need to wait for a queue of redundant workflows to finish.
|
| | |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Some of our deps don't have wheels for atm processors.
With Mac's M1 chips becomming more common, we should make it easier for those users to build our environments.
|
| |\ \ \ \
| | | | |
| | | | | |
Update deployment manifest path
|
| |/ / / / |
|