CI: fix workflows and add PyPI publish flow #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci-pypi-publish"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Work in progress: fixes the known-red forgejo Actions test workflow (blocked pypi.org egress on self-hosted runners) and adds a real PyPI publish flow, per https://code.gierz.xyz/paul/paleodatetime known-red note in .forgejo/workflows/test.yml.
Status: blocked pending egress being opened on the self-hosted runners (cariconnect-de, gierz-services) to pypi.org, files.pythonhosted.org, upload.pypi.org, test.pypi.org/test-files.pythonhosted.org, and objects.githubusercontent.com (only if actions/setup-python stays in publish.yml).
So far: added project.urls metadata for the PyPI listing page. Test/publish workflow fixes to follow once egress is confirmed open.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.