Parallel uploads to a release
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The issue names no files or tests; start by examining github-release-cli's release creation and upload flow, with attention to how parallel Travis CI VMs identify the target release. Reproduce three concurrent uploads and verify that they add files to one defined release rather than creating separate releases.
Written by the indexing model from the issue text.
Description
I am using Travis CI to run 3 VMs in parallel to create 3 different binaries of my application. The releaser is properly setting up the release and including my body text as expected. However, it is creating 3 independent releases instead of adding all of the uploads from the independent VMs to the same defined release.
Is there something that I am missing to have all 3 VMs upload to the same release?
- Dominant language
- Go
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
More from lindell/github-release-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in lindell/github-release-cli
Similar issues
-
kind/bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
matrixorigin/matrixone#29223 ·
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
alexgorbatchev/dotfiles#107 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100