| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
|\| |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
I've renamed the file to create a more consistent naming scheme.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
I've restructured the build & deploy sequence in our GitHub Actions CI
workflow:
- There's now a separate workflow to deploy to our cluster
- The Build workflow has an additional `if` check to ensure we're only
starting the build & deploy sequences for pushes to master
- We now checkout the python-discord/kubernetes repo to fetch the
deployment.yaml file located in there
|
|
|
| |
The CI was failing on occasion because postgres did not have time enough to start properly before we started running our makemigrations check. I've moved the docker-compose step to earlier in the workflow to give it some time to warm up.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unfortunately, the way we previously set up our workflow caused flake8
to run on code already committed to master, not the changes made in a
PR, because it ran in the context of the target branch.
This is obviously useless when it comes to protecting our codebase from
linting errors. I've now set up flake8 in a different way, using
Workflow Commands to create error annotions.
I've also split up the workflow into two separate workflows.
|
| |
|
| |
|
|
|
| |
This makes it clearer that the env var switches on or off "CI-mode"
|
|
|
|
|
|
| |
I've migrated site to GitHub Actions and GitHub Container Registry. This
also means that coverage results will be pushed to coveralls.io. This
commit also removes the pretty useless codeql analysis action.
|
|
|
|
|
| |
This should be all we need to enable the releases feature in Sentry for
this project.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|