ci: publish workflow should not upload artifacts for master branch
Open
Nobody has claimed this yet.
1sp
teamE
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
Publish workflow should not upload artifacts on push to master branch.
- push to master: test goreleaser build
- new tag: test goreleaser build + upload artifacts
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 locating the publish workflow and reviewing its push-to-master and new-tag triggers, then check how the GoReleaser build and artifact upload steps are gated. Done means pushes to master test the GoReleaser build without uploading artifacts, while new tags test the build and upload artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100