site - A mirrored copy of the python-discord/site repository.

	Commit message (Collapse)	Author	Lines
2020-11-24	Restructure Build & Deploy sequence in CI	Sebastiaan Zeeff	-41/+49
	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
2020-11-21	Change seasonalbot to sir-lancebot in test data	Sebastiaan Zeeff	-1/+1

2020-11-21	Change seasonalbot to sir-lancebot	Sebastiaan Zeeff	-1/+1

2020-11-19	Start database at the beginning of the workflow	Sebastiaan Zeeff	-3/+5
	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.
2020-11-19	Insert missing "jobs" yaml tag	Sebastiaan Zeeff	-1/+1

2020-11-19	Update badges in README to reflect new workflows	Sebastiaan Zeeff	-8/+15
	I've also restructured it a bit by using reference links instead of inline links.
2020-11-19	Ensure that flake8 runs on PR changes	Sebastiaan Zeeff	-67/+83
	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.
2020-11-15	Default to HTTPS for account URLs	Joe Banks	-0/+1

2020-11-15	Bump version down to 3.8	Leon Sandøy	-5/+5

2020-11-15	Update readme badge	Joe Banks	-1/+1

2020-11-15	Update build flow to deploy to Kubernetes	Joe Banks	-2/+17