gh-action-pypi-publish

Open
#100 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, python
Domain
ci-cd, release

Research direction

Start with .github/workflows/pypi-release.yml and inspect how the current PyPI release workflow is triggered and published. Compare adding skip_existing: true with restricting the workflow to tagged commits; the work is done when the chosen approach allows the intended README adjustments to be released without undesirable duplicate-publication behavior.

Written by the indexing model from the issue text.

Description

We may want to add the following to pypi_release.yml:

with:
    skip_existing: true

to enable readme adjustments pushed to master. Unsure if this is the best way of handling this, or if the workflow should be changed to only allowing tagged commits

Dominant language
Python
Stars
342
Forks
65
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudevents/sdk-python

All issues in cloudevents/sdk-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.