jaraco / jaraco/jaraco.develop
Create GitHub release should be lenient to existing releases
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 5
- Avg merge
- 20m
- Merged PRs (30d)
- 1
Description
In reubano/meza#66, I learned that the `create-github-release` script will fail if the release already exists. But in the case of some projects, it may be desirable to tag a new release by using the GitHub create release feature. In fact, it may not be possible to create a tag without creating a release ([confirmed](https://g.co/gemini/share/ea3b10a74fcf)).
I'd like to consider options for this project to facilitate such workflows, such as:
- Be lenient to an existing release (what happens to the assets and release notes, if present?).
- Allow an option to ignore existing releases.
- Fail with a predictable code for easy suppression.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the create-github-release script and trace how it handles a release that already exists. Compare the possible behaviors described in the issue, including assets, release notes, optional ignoring, and predictable failure, then define the selected behavior and its completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100