Error annotations during release workflow
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Like this
Build Cross-Platform Binaries (darwin, amd64, darwin-amd64)
Cannot open: File exists
Maybe they have always been there, I only checked the last two releases
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 opening the linked GitHub Actions runs for v0.1.0 and v0.2.0 and inspect the Build Cross-Platform Binaries job logs. Compare the darwin/amd64 output to determine where the “Cannot open: File exists” annotation originates. Done means the release workflow no longer reports this error, or the cause and expected behavior are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, cli, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100