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

	Commit message (Collapse)	Author	Age	Lines
*	Make sure to always upload PR artifact	Sebastiaan Zeeff	2020-12-11	-1/+1
\| \| \|	We need to make sure that we always upload our PR artifact, even if linting/testing fails. As GitHub Actions inserts an implicit "success" status check if you don't add any explicit status checks, this means that we have to include an "always" status check, even if this step has a condition relying on another "always" step.
*	Send an enhanced workflow status embed to discord	Sebastiaan Zeeff	2020-12-10	-0/+22
\| \| \| \| \| \|	Similar to Sir Lancebot and bot, I've added enhanced GitHub Actions status embeds to our workflow sequence. This means we get fewer embeds, but with more information!
*	Start database at the beginning of the workflow	Sebastiaan Zeeff	2020-11-19	-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.
*	Ensure that flake8 runs on PR changes	Sebastiaan Zeeff	2020-11-19	-0/+118
	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.