marceloavf / marceloavf/github-tools-vsts
Allow to clear assets release
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 25
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
- [x] **Bug** - If try to send the asset with the same name, it will not override the file.
- [ ] **Enhancement** - If the release already exists, allow to clear it (remove all assets or delete the release) and send the new one
- [x] **Enhancement** - If the release already exists, allow to clear it (remove only this specific assets) and send the new one
Contributor guide
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 entry points are named. Trace the JavaScript release-upload path for an existing release, then determine how the release or its assets can be cleared before sending the replacement. Done means a new asset can be sent after clearing the existing release contents without leaving the old assets in place.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100