Skip to content

Commit

Permalink
Add manual trigger for package publishing
Browse files Browse the repository at this point in the history
This is probably the wrong way to do it, but the docs for workflows do
not show how to use multiple on triggers when one of them is more
complex than a top level option.

Signed-off-by: Eric B Munson <[email protected]>
  • Loading branch information
khers committed Jun 12, 2024
1 parent a44b27f commit 3d7ad75
Showing 1 changed file with 38 additions and 0 deletions.
38 changes: 38 additions & 0 deletions .github/workflows/python-publish-manual.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# This workflow will upload a Python Package using Twine when a release is created
# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries

# This workflow uses actions that are not certified by GitHub.
# They are provided by a third-party and are governed by
# separate terms of service, privacy policy, and support
# documentation.

name: Upload Python Package

on: [workflow_dispatch]

permissions:
contents: read

jobs:
deploy:

runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v4
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: '3.x'
- name: Install dependencies
run: |
python -m pip install --upgrade pip
pip install build setuptools wheel
pip install -r requirements.txt
- name: Build package
run: python -m build
- name: Publish package
uses: pypa/gh-action-pypi-publish@27b31702a0e7fc50959f5ad993c78deac1bdfc29
with:
user: __token__
password: ${{ secrets.PYPI_API_TOKEN }}

0 comments on commit 3d7ad75

Please sign in to comment.