aboutsummaryrefslogtreecommitdiffstats
path: root/bot/bot.py (unfollow)
Commit message (Collapse)AuthorLines
2020-11-21Remove dead ShowProjects cog.Gravatar Leon Sandøy-1/+1
We no longer have this channel, so this cog serves no purpose.
2020-11-21Remove references to old name.Gravatar Leon Sandøy-89/+82
I've tried to replace this with generic references where appropriate, but a lot of the time it just doesn't make a lot of sense to do so.
2020-11-21Make the bot name less hard-coded.Gravatar Leon Sandøy-19/+22
2020-11-20Simpler environment variables.Gravatar Leon Sandøy-6/+6
Co-authored-by: Jeremiah Boby <[email protected]>
2020-11-20Add inline cache manifest to docker imageGravatar Sebastiaan Zeeff-0/+1
We need to attach an inline cache manifest to the image we build and push to the GHCR to be able to use the registry as a cache source for subsequent builds. I've added it to the build workflow configuration.configuration.
2020-11-19Update workflow status badges in readmeGravatar Sebastiaan Zeeff-1/+7
Our two workflows, Lint and Build, now have separate status badges that link to the latest results from that workflow.
2020-11-17Get rid from branding management stuffGravatar ks129-836/+5
2020-11-16Remove unnecessary JSON filesGravatar ks129-5/+0
2020-11-16Port HacktoberStats cog to use Redis instead of JSONGravatar ks129-67/+12
2020-11-16Port candy_collection.py to use Redis instead of JSONGravatar ks129-34/+26
2020-11-16Split lint and build jobs into separate workflowsGravatar Sebastiaan Zeeff-57/+66
I've separated the lint and build jobs into two separate workflows: - Lint: .github/workflows/lint.yaml - Build: .github/workflows/build.yaml The main difference is that the Build workflow will be triggered if the Lint workflow completes while it's been run on the "master" branch. The build job will check if the Lint run was successful and if it were, it actually builds the container, pushes it the GHCR, and triggers the deployment to our kubernetes cluster.
2020-11-16Migrate branding from JSON persist to RedisGravatar ks129-25/+13
2020-11-16Depend bot on redis, add other environment variables + sync filesGravatar ks129-4/+7
2020-11-16Fix lint errors introduced by persistence removalGravatar Sebastiaan Zeeff-8/+8
We ripped some features out of the bot to make the migration to kubernetes easier. However, that process left us with some linting errors that will play up if anyone makes a PR. I've added "noqa" to the valid TODO lines and commented out lines that introduced now unused names or tried to use now undefined names. This should have no influence on the bot, as it does not touch code that is actually being run at the moment.
2020-11-16Relay seasonalbot token and debug to docker-compose.ymlGravatar ks129-2/+2
2020-11-16Implement Redis connection to bot class and create instanceGravatar ks129-2/+26
2020-11-16Ensure flake8 runs correctly in Pull Request checkGravatar Sebastiaan Zeeff-13/+11
Unfortunately, the flake8 action we were using from the marketplace required us to use the `pull_request_target` event, which runs in the context of the target repository to protect secrets. However, this also meant that flake8 would run on files already merged into our master branch, not the actual changes made in teh PR! That's obviously pretty useless as a guard against merging linting errors into our repository. This change sidesteps the issue by removing the marketplace action and replacing it by a direct `flake8` run command. To make sure error output ends up as a GitHub Actions Annotation, we ask `flake8` to format its error messages using the correct GitHub Workflow Command format: ::error file={filename},line={line},col={col}::{message} Whenever something is printed to stdout/stderr in that format, GitHub Actions will automatically interpret it as the "register error message" workflow command. Since this doesn't require a GitHub Token with "write" permissions, we can now switch back to the safer `pull_request` event that gets a read-only GitHub Token.
2020-11-16Rename redis configuration classGravatar ks129-1/+2
2020-11-16Put development Redis information to containerGravatar ks129-0/+1
2020-11-16Create Redis configuration classGravatar ks129-0/+7
2020-11-16Add Redis service to docker-compose.ymlGravatar ks129-0/+5
2020-11-16Add async-rediscache dependency to PipfileGravatar ks129-19/+113
2020-11-15Remove DockerHub from GitHub ActionsGravatar Sebastiaan Zeeff-11/+3
We're no longer using DockerHub in our deployment for SeasonalBot, so it does not make sense to keep pushing containers there.
2020-11-15Change CI badge to GitHub ActionsGravatar Sebastiaan Zeeff-1/+1
2020-11-14Merge build and deploy stagesGravatar Joe Banks-19/+2