| Commit message (Collapse) | Author | Lines |
|
Reusable workflows don't have access to secrets, even in this case where
the workflow is local.
|
|
There are no pipes the in script, so the presence of -o pipefail may
confuse readers.
|
|
The latter is consistent with GitHub Action's documentation.
|
|
There isn't enough "meat" to warrant their use.
|
|
Co-authored-by: wookie184 <[email protected]>
|
|
Also remove the reliance on the container needing to mount the host's
files to the same directory during local testing.
Fix #135
|
|
|
|
Use docker-compose run instead of docker-compose up. This is more
appropriate since the container is only needed for one command. The
latter was actually starting the whole snekbox server. Furthermore,
the former has the --rm option to remove the container when the command
finishes.
As an extra precaution, use docker-compose down in the self-hosted
runner to also remove images, volumes, networks, and any other
containers that were somehow missed. Removing images will also prevent
the disk usage from building up. This is not necessary for the GH-hosted
runner since a new VM is used for each run.
|
|
No more mocks!
|
|
The step was running even if the pre-commit hooks step never ran.
|
|
|
|
Remove the dependency on the container so the lint job can run in
parallel with the build job. More time has to be spent installing
Python dependencies, but this is made up for by not having to download
and load the image artefact in addition to not having to wait for the
build job.
|
|
See https://github.com/TheKevJames/coveralls-python/issues/240
|
|
Unlike the cache action, the build-push action's GHA cache feature
seems to only do an exact comparison for the scope. Thus, new commits
lead to cache misses.
|
|
|
|
Make the artefact and file names identical to simplify things. The
artefact name doesn't have to be unique anyway since it can only be
downloaded by the same workflow run.
|
|
|
|
load: true was already creating a tarball, but it was getting
immediately loaded. Since no other Docker builds run in this job,
it's useless to load it. The action can still be leveraged to create
the tarball instead of manually invoking `docker save`.
|
|
|