Create GitHub release should be lenient to existing releases
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
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.
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).
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.
- Dominant language
- Python
- Stars
- 7
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from jaraco/jaraco.develop
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
jaraco/jaraco.develop#22 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
jaraco/jaraco.develop#13 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
jaraco/jaraco.develop#8 · 4 comments ·
All issues in jaraco/jaraco.develop
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
NVIDIA/flare-local-inference#90 ·
Maintainers usually reply within 1 day
-
area/streaming comp/gateway P2 platform/telegram type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#144897 ·
Maintainers usually reply within 1 day
-
request-theme
Difficulty 1/5 Under an hour Newbie friendliness 66/100
LizardByte/ThemerrDB#9575 ·
Maintainers usually reply within 1 day
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
acl-org/acl-anthology#10599 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zilliztech/memsearch#818 ·
Maintainers usually reply within 1 day