psychedelicious 5bf61382a4 feat: add python dist as release artifact, as input to enable publish to pypi ... - The release workflow never runs automatically. It must be manually kicked off. - The release workflow has an input. When running it from the GH actions UI, you will see a "Publish build on PyPi" prompt. If this value is "true", the workflow will upload the build to PyPi, releasing it. If this is anything else (e.g. "false", the default), the workflow will build but not upload to PyPi. - The `dist/` folder (where the python package is built) is uploaded as a workflow artifact as a zip file. This can be downloaded and inspected. This allows "dry" runs of the workflow. - The workflow job and some steps have been renamed to clarify what they do		2023-12-16 20:02:09 +11:00
..
build-container.yml	(ci) remove testing branch	2023-07-12 16:51:15 -04:00
clean-caches.yml	add workflow to clean caches after PR gets closed	2023-02-01 18:32:29 +01:00
close-inactive-issues.yml	uses v8 actions/stale@v8	2023-07-25 11:23:00 +10:00
lint-frontend.yml	fix: use node 18, set working directory	2023-12-16 00:32:31 +11:00
mkdocs-material.yml	fix mkdocs push	2023-07-21 12:27:53 -04:00
pypi-release.yml	feat: add python dist as release artifact, as input to enable publish to pypi	2023-12-16 20:02:09 +11:00
style-checks.yml	change stylecheck name from "black" to "ruff"	2023-11-14 11:06:10 -05:00
test-invoke-pip.yml	deploy: refactor github workflows	2023-08-03 10:32:50 +10:00