| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
| |
Still a work in progress but commenting out stub code and unused
imports. List of To-Do's still applies.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Implemented the thumbnail creation from CyberCitizen0,
worked on adding some features to the program.
Notable Changes:
-Check if user passes in hex color
-Create thumbnail based on rgb_color
To-Do:
-Create hex color from rgb color
-Create readable rgb color from user input
Co-authored-by: Mohammad Rafivulla <[email protected]>
|
| | |\
| | |
| | |
| | | |
color-677
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* CI: check for license compatibility
Port of https://github.com/python-discord/bot/pull/1779
---
Since our project is licensed under the MIT License, we can't be using any incompatible license-wise dependencies in our project, such as GPL.
This commit adds a step to the CI lint phase that will use pip-licenses to verify that all the installed packages are part of an ALLOWED_LICENSE variable. This variable is currently set to be every license we currently use.
We opted to use an allowlist instead of a denylist to make sure that new licenses are reviewed by hand and added to that variable.
Co-authored-by: ChrisJL <[email protected]>
Co-authored-by: Xithrius <[email protected]>
Co-authored-by: Vivaan Verma <[email protected]>
|
| | | |\
| | | |
| | | | |
Set logging level for async-rediscache to warning
|
| | | | |\
| | | |/
| | |/| |
|
| | | | |
| | | |
| | | |
| | | | |
Logs below warnings aren't relevant when working on the bot
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |\| | |
|
| | | |\ \
| | | | |
| | | | | |
Post re-structure fixs
|
| | | | | | |
|
| | | |/ / |
|
| | | |\ \
| | | |/
| | |/| |
Restructure Sir Lancebot
|
| | | | |\
| | | |/
| | |/| |
|
| | | |\ \
| | | | |
| | | | | |
Pin platform in Dockerfile
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This moves all the fun commands and games into the fun folder.
This commit also makes changes to the duck_game.
It was setting a footer during an embed init, which is no longer
possible with the version of d.py we use. Additionally, an issue with
editing an embed that had a local image loaded.
The workaround for the time being is to update the message,
not the embed.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Separates out the useful/practical seasonal bot features from the
evergreen folder into a "utilities" folder.
Adjusts the paths to resources to reflect the folder move.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Part of this restructure involves splitting out the massive evergreen
folder into a `fun` folder and then a `utilities` folder. To help with
that we've rename the `util` folder to `core`.
The core functions to run the bot have been moved into this folder.
`.source`, `.ping`, and `.int e` have been moved into this folder.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Additionally, this commit fixes an error with the pridepfp command.
The avatar image now uses discord.py's v.20 avatar.url instead
of avatar_url
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Hannukah was previously in the Christmas folder, which was weird.
This now moves it to its own folder under Holidays.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Moves the Pride features to the Holidays folder.
Corrected the paths to reflect this change.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Moves the valentine's day features to the holidays folders.
Corrected the paths to reflect the folder moves.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Moves all the hallowen features to the holidays folder.
Also updates the paths to reflect the folder moves.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This moves the easter seasonal features into a more cohesive
holidays/easter folder. Additionally, this splits out earth day into
its own holiday folder.
|
| | | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Moves Advent of Code and Hacktoberfest into an events
folder. Although these are roughly associated with holidays,
they are standalone events that we have participated in
in the past.
Therefore they're being moved to an events folder
separate from the "fun" or "holidays" folders.
|
| | | |\
| | | |
| | | | |
Update manifest path
|
| | | |/ |
|
| | | |\
| | | |
| | | | |
Teapot support - Continues PR #610
|
| | | | |\
| | | |/
| | |/| |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Hard-coded in the appropriate 404 jpgs for wehn a status code does
not exist from the dog or cat urls.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The unknown error embed was not using the text correctly,
using the suggestion from wookie to fix.
The "404" response from the dog URL returns 302 instead,
changed the elif to check if 302 response is returned.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Changed the range check for the status code.
Previously was 599, now 600.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Corrected the URL for the Dog embed (was mistakenly using CAT URL.
Created a standalone ERROR_LENGTH_EMBED to send if the code used
by the user is not in the range 100, 599.
Changed the response status check to include 299 (to be proper).
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This will avoid sending the error embed even when the status codes
are ok.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Also updated the line breaks, black was formatting on save locally.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now that the branch is correctly tracking only the changes to the
file `status_codes.py` the other requests can be addressed. Currently
the only change not addressed is to handle the range of responses
allowed. My focus will be on lines 45 to 64 for these changes.
Issues #428 #500 #608
PR #610
|
| | | | |\ |
|
| | | | | | |
|
| | | | | | |
|
| | | | |\ \ |
|