semantic-release / semantic-release/github
How to execute "success" step manually after its failure?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
During release, my script has faced github rate limiting and the success step has failed, whereas the release itself was successful: its tag has been committed, but no "success" comments were added to the corresponding issues and pull requests.
I would like to trigger "success" step one more time, but I'm not sure how to do that.
Now it simply says "there are no change since last release".
Could you help?
Basically, I need to run the "success" step for "github" only between versions "14.10.1" and "14.11.0".
Thank you in advance.
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
No files, tests, or implementation entry points are named. Start by reviewing how the GitHub plugin handles the release and success step, focusing on versions 14.10.1 through 14.11.0; done means documenting whether and how the GitHub-only success step can be rerun after rate limiting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100